From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: [PATCH libc-test] add utime (utimensat, futimens) functional tests
Date: Thu, 22 Aug 2019 21:04:36 -0400 [thread overview]
Message-ID: <20190823010436.GN9017@brightrain.aerifal.cx> (raw)
[-- Attachment #1: Type: text/plain, Size: 168 bytes --]
Here's a WIP (may extend later but seems good as-is too) utime test
for libc-test. I've been using it to test the upcoming time64
functionality for 32-bit archs.
Rich
[-- Attachment #2: 0001-add-utime-utimensat-futimens-functional-tests.patch --]
[-- Type: text/plain, Size: 3453 bytes --]
From abffbd450401c6638177c0bc7b789130e41c1e84 Mon Sep 17 00:00:00 2001
From: Rich Felker <dalias@aerifal.cx>
Date: Thu, 22 Aug 2019 20:58:00 -0400
Subject: [PATCH] add utime (utimensat, futimens) functional tests
these tests check for the ability to set file timestamps using
UTIME_NOW, UTIME_OMIT, and explicit timespecs. they indirectly check
that fstat works as well, and include a check of the first Y2038
timestamp that overflows 32-bit time_t, reporting errors for a Y2038
EOL implementaton (if time_t is 32-bit) or a kernel, filesystem, or
library implementation that fails to set and read back timestamps past
the 32-bit limit despite having a time_t type that can represent such
a timestamp.
---
src/functional/utime.c | 73 ++++++++++++++++++++++++++++++++++++++++++
1 file changed, 73 insertions(+)
create mode 100644 src/functional/utime.c
diff --git a/src/functional/utime.c b/src/functional/utime.c
new file mode 100644
index 0000000..7fa7a1f
--- /dev/null
+++ b/src/functional/utime.c
@@ -0,0 +1,73 @@
+#include <sys/stat.h>
+#include <errno.h>
+#include <string.h>
+#include <stdio.h>
+#include <time.h>
+#include <stdint.h>
+#include <unistd.h>
+#include <fcntl.h>
+#include "test.h"
+
+#define TEST(c, ...) ((c) ? 1 : (t_error(#c" failed: " __VA_ARGS__),0))
+#define TESTVAL(v,op,x) TEST(v op x, "%jd\n", (intmax_t)(v))
+
+int main(void)
+{
+ struct stat st;
+ FILE *f;
+ int fd;
+ time_t t;
+
+ TEST(utimensat(AT_FDCWD, "/dev/null/invalid", ((struct timespec[2]){{.tv_nsec=UTIME_OMIT},{.tv_nsec=UTIME_OMIT}}), 0)==0 || errno==ENOTDIR,
+ "%s\n", strerror(errno));
+ TEST(futimens(-1, ((struct timespec[2]){{.tv_nsec=UTIME_OMIT},{.tv_nsec=UTIME_OMIT}}))==0 || errno==EBADF,
+ "%s\n", strerror(errno));
+
+ if (!TEST(f = tmpfile())) return t_status;
+ fd = fileno(f);
+
+ TEST(futimens(fd, (struct timespec[2]){0}) == 0, "\n");
+ TEST(fstat(fd, &st) == 0, "\n");
+ TESTVAL(st.st_atim.tv_sec,==,0);
+ TESTVAL(st.st_atim.tv_nsec,==,0);
+ TESTVAL(st.st_mtim.tv_sec,==,0);
+ TESTVAL(st.st_mtim.tv_nsec,==,0);
+
+ TEST(futimens(fd, ((struct timespec[2]){{.tv_sec=1,.tv_nsec=UTIME_OMIT},{.tv_sec=1,.tv_nsec=UTIME_OMIT}})) == 0, "\n");
+ TEST(fstat(fd, &st) == 0, "\n");
+ TESTVAL(st.st_atim.tv_sec,==,0);
+ TESTVAL(st.st_atim.tv_nsec,==,0);
+ TESTVAL(st.st_mtim.tv_sec,==,0);
+ TESTVAL(st.st_mtim.tv_nsec,==,0);
+
+ t = time(0);
+
+ TEST(futimens(fd, ((struct timespec[2]){{.tv_nsec=UTIME_NOW},{.tv_nsec=UTIME_OMIT}})) == 0, "\n");
+ TEST(fstat(fd, &st) == 0, "\n");
+ TESTVAL(st.st_atim.tv_sec,>=,t);
+ TESTVAL(st.st_mtim.tv_sec,==,0);
+ TESTVAL(st.st_mtim.tv_nsec,==,0);
+
+ TEST(futimens(fd, (struct timespec[2]){0}) == 0, "\n");
+ TEST(futimens(fd, ((struct timespec[2]){{.tv_nsec=UTIME_OMIT},{.tv_nsec=UTIME_NOW}})) == 0, "\n");
+ TEST(fstat(fd, &st) == 0, "\n");
+ TESTVAL(st.st_atim.tv_sec,==,0);
+ TESTVAL(st.st_mtim.tv_sec,>=,t);
+
+ TEST(futimens(fd, ((struct timespec[2]){{.tv_nsec=UTIME_NOW},{.tv_nsec=UTIME_OMIT}})) == 0, "\n");
+ TEST(fstat(fd, &st) == 0, "\n");
+ TESTVAL(st.st_atim.tv_sec,>=,t);
+ TESTVAL(st.st_mtim.tv_sec,>=,t);
+
+ if (TEST((time_t)(1LL<<32) == (1LL<<32), "implementation has Y2038 EOL\n")) {
+ if (TEST(futimens(fd, ((struct timespec[2]){{.tv_sec=1LL<<32},{.tv_sec=1LL<<32}})) == 0, "%s\n", strerror(errno))) {
+ TEST(fstat(fd, &st) == 0, "\n");
+ TESTVAL(st.st_atim.tv_sec, ==, 1LL<<32);
+ TESTVAL(st.st_mtim.tv_sec, ==, 1LL<<32);
+ }
+ }
+
+ fclose(f);
+
+ return t_status;
+}
--
2.21.0
next reply other threads:[~2019-08-23 1:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-23 1:04 Rich Felker [this message]
2019-10-31 1:49 ` Szabolcs Nagy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190823010436.GN9017@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=musl@lists.openwall.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).