From: Matthew Wilcox <willy@infradead.org>
To: Linux regressions mailing list <regressions@lists.linux.dev>
Cc: yangerkun <yangerkun@huawei.com>,
"Christian Brauner" <brauner@kernel.org>,
linux-fsdevel@vger.kernel.org,
"Alexander Viro" <viro@zeniv.linux.org.uk>,
LKML <linux-kernel@vger.kernel.org>,
"Krzysztof Małysa" <varqox@gmail.com>
Subject: Re: [regression] getdents() does not list entries created after opening the directory
Date: Tue, 1 Oct 2024 13:18:36 +0100 [thread overview]
Message-ID: <ZvvonHPqrAqSHhgV@casper.infradead.org> (raw)
In-Reply-To: <8196cf54-5783-4905-af00-45a869537f7c@leemhuis.info>
On Tue, Oct 01, 2024 at 01:29:09PM +0200, Linux regression tracking (Thorsten Leemhuis) wrote:
> > DIR* dir = opendir("/tmp/dirent-problems-test-dir");
> >
> > fd = creat("/tmp/dirent-problems-test-dir/after", 0644);
"If a file is removed from or added to the directory after the most
recent call to opendir() or rewinddir(), whether a subsequent call to
readdir() returns an entry for that file is unspecified."
https://pubs.opengroup.org/onlinepubs/007904975/functions/readdir.html
That said, if there's an easy fix here, it'd be a nice improvement to
QoI to do it, but the test-case as written is incorrect.
next prev parent reply other threads:[~2024-10-01 12:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-01 11:29 [regression] getdents() does not list entries created after opening the directory Linux regression tracking (Thorsten Leemhuis)
2024-10-01 12:18 ` Matthew Wilcox [this message]
2024-10-01 12:49 ` Linux regression tracking (Thorsten Leemhuis)
2024-10-01 18:59 ` Christian Heusel
2024-10-01 19:15 ` Krzysztof Małysa
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=ZvvonHPqrAqSHhgV@casper.infradead.org \
--to=willy@infradead.org \
--cc=brauner@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--cc=varqox@gmail.com \
--cc=viro@zeniv.linux.org.uk \
--cc=yangerkun@huawei.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.
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).