From: "Thomas Weißschuh" <linux@weissschuh.net>
To: Daniel Palmer <daniel@thingy.jp>
Cc: w@1wt.eu, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] selftests/nolibc: Add test for dirfd()
Date: Wed, 7 Oct 2026 10:09:27 +0200 [thread overview]
Message-ID: <0d1cbffe-812f-4882-a315-7ad41a3fe1a7@t-8ch.de> (raw)
In-Reply-To: <20261007052914.888956-3-daniel@thingy.jp>
Hi Daniel,
On 2026-10-07 14:29:13+0900, Daniel Palmer wrote:
> Test that open() and dirfd() use the same fd and then use
> dirfd() with fstatat() to stat each of its children.
In general the series looks good. I have some minor requests,
but can also implement these myself if you prefer.
Also I'd like to push the patches into the next development cycles.
> Signed-off-by: Daniel Palmer <daniel@thingy.jp>
> ---
> tools/testing/selftests/nolibc/nolibc-test.c | 47 ++++++++++++++++++++
> 1 file changed, 47 insertions(+)
>
> diff --git a/tools/testing/selftests/nolibc/nolibc-test.c b/tools/testing/selftests/nolibc/nolibc-test.c
> index ed860b0a15a1..82616f2c1ba4 100644
> --- a/tools/testing/selftests/nolibc/nolibc-test.c
> +++ b/tools/testing/selftests/nolibc/nolibc-test.c
> @@ -858,6 +858,52 @@ static int test_dirent(void)
> return 0;
> }
>
> +static int test_dirfd(void)
> +{
> + struct dirent dirent, *result;
> + int ret = 0, fd;
> + struct stat st;
> + DIR *dir;
> +
> + fd = open("/", O_RDONLY | O_DIRECTORY);
> + if (fd < 0)
> + return __LINE__;
> +
> + dir = fdopendir(fd);
> + if (!dir) {
> + close(fd);
> + return __LINE__;
> + }
> +
> + /* Check that dirfd() gives the same fd as open() */
> + if (dirfd(dir) != fd) {
> + ret = __LINE__;
> + goto out;
> + }
> +
> + /* Loop through the children of the directory calling fstatat() on each */
What is the advantage of reading all entries here?
We already do something similar in test_dirent().
Reading a single entry should be enough.
> + while (1) {
> + if (readdir_r(dir, &dirent, &result) != 0) {
> + ret = __LINE__;
> + goto out;
> + }
> +
> + if (!result)
> + break;
> +
> + if (fstatat(dirfd(dir), dirent.d_name, &st, AT_SYMLINK_NOFOLLOW) != 0) {
> + ret = __LINE__;
> + goto out;
> +
> + }
> + }
> +
> +out:
> + closedir(dir);
> +
> + return ret;
> +}
> +
> int test_getcwd(void)
> {
> char cwd_syscall[PATH_MAX];
> @@ -1651,6 +1697,7 @@ int run_syscall(int min, int max)
> CASE_TEST(getdents64_root); EXPECT_SYSNE(1, test_getdents64("/"), -1); break;
> CASE_TEST(getdents64_null); EXPECT_SYSER(1, test_getdents64("/dev/null"), -1, ENOTDIR); break;
> CASE_TEST(directories); EXPECT_SYSZR(is_nolibc && proc, test_dirent()); break;
> + CASE_TEST(dirfd); EXPECT_SYSZR(is_nolibc, test_dirfd()); break;
Could you mention in the commit message why this is specific to nolibc?
> CASE_TEST(getrandom); EXPECT_SYSZR(1, test_getrandom()); break;
> CASE_TEST(gettimeofday_tv); EXPECT_SYSZR(1, gettimeofday(&tv, NULL)); break;
> CASE_TEST(gettimeofday_tv_tz);EXPECT_SYSZR(1, gettimeofday(&tv, &tz)); break;
> --
> 2.53.0
>
next prev parent reply other threads:[~2026-10-07 8:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-07 5:29 [PATCH v2 0/2] nolibc: Add dirfd() Daniel Palmer
2026-10-07 5:29 ` [PATCH v2 1/2] tools/nolibc: " Daniel Palmer
2026-10-07 8:03 ` Thomas Weißschuh
2026-10-08 7:59 ` David Laight
2026-10-07 5:29 ` [PATCH v2 2/2] selftests/nolibc: Add test for dirfd() Daniel Palmer
2026-10-07 8:09 ` Thomas Weißschuh [this message]
2026-10-07 6:43 ` [PATCH v2 0/2] nolibc: Add dirfd() Willy Tarreau
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=0d1cbffe-812f-4882-a315-7ad41a3fe1a7@t-8ch.de \
--to=linux@weissschuh.net \
--cc=daniel@thingy.jp \
--cc=linux-kernel@vger.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®