From: Andreas Schwab <schwab@suse.de>
To: Florian Weimer <fweimer@redhat.com>
Cc: Florian Weimer via Libc-alpha <libc-alpha@sourceware.org>
Subject: Re: [PATCH] Linux: Do not skip d_ino == 0 entries in readdir, readdir64 (bug 12165)
Date: Mon, 19 Sep 2022 11:58:32 +0200 [thread overview]
Message-ID: <mvmpmfrr8hj.fsf@suse.de> (raw)
In-Reply-To: <878rmfhfsv.fsf@oldenburg.str.redhat.com> (Florian Weimer's message of "Mon, 19 Sep 2022 11:30:40 +0200")
On Sep 19 2022, Florian Weimer wrote:
> What about this?
>
> /* Linux may fail with ENOENT on some file systems if the
> directory inode is marked as dead (deleted). POSIX
> treats this as a regular end-of-directory condition, so
> do not set errno in that case, to indicate success. */
Ok.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
prev parent reply other threads:[~2022-09-19 9:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-19 6:54 Florian Weimer
2022-09-19 8:26 ` Andreas Schwab
2022-09-19 8:30 ` Florian Weimer
2022-09-19 8:53 ` Andreas Schwab
2022-09-19 9:30 ` Florian Weimer
2022-09-19 9:58 ` Andreas Schwab [this message]
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=mvmpmfrr8hj.fsf@suse.de \
--to=schwab@suse.de \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).