From: Andreas Schwab <schwab@linux-m68k.org>
To: Florian Weimer via Libc-alpha <libc-alpha@sourceware.org>
Cc: Mark Olesen <markjolesen@gmail.com>,
Florian Weimer <fweimer@redhat.com>
Subject: Re: readdir and ENOENT error or EOF?
Date: Tue, 22 Jun 2021 10:18:23 +0200 [thread overview]
Message-ID: <877dimmhww.fsf@igel.home> (raw)
In-Reply-To: <87y2b2e3n1.fsf@oldenburg.str.redhat.com> (Florian Weimer via Libc-alpha's message of "Tue, 22 Jun 2021 09:53:54 +0200")
On Jun 22 2021, Florian Weimer via Libc-alpha wrote:
> * Mark Olesen:
>
>> Should ENOENT be handled as an error or is it indeed an EOF condition?
>
> I don't know. It's really hard to make such changes because there are
> so many Linux file system implementations. So we kind of default to
> make not making changes. 8-/
POSIX makes it clear that when an EOF condition occurs, errno must be
left unchanged. AFAICS, our readdir implementation conforms to that.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
prev parent reply other threads:[~2021-06-22 8:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-16 20:49 Mark Olesen
2021-06-17 7:07 ` Florian Weimer
2021-06-18 18:02 ` Mark Olesen
2021-06-22 7:53 ` Florian Weimer
2021-06-22 8:18 ` 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=877dimmhww.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=markjolesen@gmail.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 read-only IMAP folder(s) and NNTP newsgroup(s).