From: "Thomas Weißschuh" <linux@weissschuh.net>
To: Louis Taylor <louis@kragniz.eu>
Cc: Willy Tarreau <w@1wt.eu>, Shuah Khan <shuah@kernel.org>,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH] tools/nolibc: add support for openat(2)
Date: Sun, 2 Mar 2025 23:24:43 +0100 [thread overview]
Message-ID: <d0ed3b0d-4b7d-40cb-bbce-1f2a6605db7f@t-8ch.de> (raw)
In-Reply-To: <20250302202528.4169024-1-louis@kragniz.eu>
Hi Louis,
On 2025-03-02 20:25:23+0000, Louis Taylor wrote:
> openat is useful to avoid needing to construct relative paths, so expose
> a wrapper for using it directly.
Can you say what you are using nolibc for? I'm curious :-)
> Signed-off-by: Louis Taylor <louis@kragniz.eu>
> ---
> tools/include/nolibc/sys.h | 29 ++++++++++++++++++++
> tools/testing/selftests/nolibc/nolibc-test.c | 22 +++++++++++++++
> 2 files changed, 51 insertions(+)
>
> diff --git a/tools/include/nolibc/sys.h b/tools/include/nolibc/sys.h
> index 8f44c33b1213..e5ff34df4aee 100644
> --- a/tools/include/nolibc/sys.h
> +++ b/tools/include/nolibc/sys.h
> @@ -765,6 +765,35 @@ int mount(const char *src, const char *tgt,
> return __sysret(sys_mount(src, tgt, fst, flags, data));
> }
>
> +/*
> + * int openat(int dirfd, const char *path, int flags[, mode_t mode]);
> + */
> +
> +static __attribute__((unused))
> +int sys_openat(int dirfd, const char *path, int flags, mode_t mode)
> +{
> +#ifdef __NR_openat
> + return my_syscall4(__NR_openat, dirfd, path, flags, mode);
> +#else
> + return __nolibc_enosys(__func__, dirfd, path, flags, mode);
> +#endif
All architectures support openat(), so the #else could be dropped.
> +}
> +
> +static __attribute__((unused))
> +int openat(int dirfd, const char *path, int flags, ...)
> +{
> + mode_t mode = 0;
> +
> + if (flags & O_CREAT) {
> + va_list args;
> +
> + va_start(args, flags);
> + mode = va_arg(args, int);
mode_t instead of int?
> + va_end(args);
> + }
> +
> + return __sysret(sys_openat(dirfd, path, flags, mode));
> +}
>
> /*
> * int open(const char *path, int flags[, mode_t mode]);
> diff --git a/tools/testing/selftests/nolibc/nolibc-test.c b/tools/testing/selftests/nolibc/nolibc-test.c
> index 79c3e6a845f3..97ded6c76f99 100644
> --- a/tools/testing/selftests/nolibc/nolibc-test.c
> +++ b/tools/testing/selftests/nolibc/nolibc-test.c
> @@ -1028,6 +1028,26 @@ int test_rlimit(void)
> return 0;
> }
>
> +int test_openat(void)
static.
> +{
> + int dev;
> + int null;
> +
> + dev = openat(AT_FDCWD, "/dev", O_DIRECTORY);
> + if (dev < 0)
> + return -1;
> +
> + null = openat(dev, "null", 0);
> + if (null < 0) {
> + close(dev);
> + return -1;
> + }
> +
> + close(dev);
> + close(null);
> +
> + return 0;
> +}
>
> /* Run syscall tests between IDs <min> and <max>.
> * Return 0 on success, non-zero on failure.
> @@ -1116,6 +1136,8 @@ int run_syscall(int min, int max)
> CASE_TEST(mmap_munmap_good); EXPECT_SYSZR(1, test_mmap_munmap()); break;
> CASE_TEST(open_tty); EXPECT_SYSNE(1, tmp = open("/dev/null", 0), -1); if (tmp != -1) close(tmp); break;
> CASE_TEST(open_blah); EXPECT_SYSER(1, tmp = open("/proc/self/blah", 0), -1, ENOENT); if (tmp != -1) close(tmp); break;
> + CASE_TEST(openat_fdcwd); EXPECT_SYSNE(1, tmp = openat(AT_FDCWD, "/dev/null", 0), -1); if (tmp != -1) close(tmp); break;
AT_FDCWD is already used in test_openat(). What additional value does
the test above add?
> + CASE_TEST(openat_dir); EXPECT_SYSNE(1, test_openat(), -1); break;
> CASE_TEST(pipe); EXPECT_SYSZR(1, test_pipe()); break;
> CASE_TEST(poll_null); EXPECT_SYSZR(1, poll(NULL, 0, 0)); break;
> CASE_TEST(poll_stdout); EXPECT_SYSNE(1, ({ struct pollfd fds = { 1, POLLOUT, 0}; poll(&fds, 1, 0); }), -1); break;
> --
> 2.45.2
>
next prev parent reply other threads:[~2025-03-02 22:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-02 20:25 Louis Taylor
2025-03-02 22:24 ` Thomas Weißschuh [this message]
2025-03-03 8:49 ` Louis Taylor
2025-03-03 9:20 ` Louis Taylor
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=d0ed3b0d-4b7d-40cb-bbce-1f2a6605db7f@t-8ch.de \
--to=linux@weissschuh.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=louis@kragniz.eu \
--cc=shuah@kernel.org \
--cc=w@1wt.eu \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®