From: Paul Eggert <eggert@cs.ucla.edu>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: libc-alpha@sourceware.org, bug-gnulib@gnu.org
Subject: Re: [PATCH v2 6/6] stdlib: Assume FACCESSAT_NEVER_EOVERFLOWS on realpath
Date: Mon, 28 Dec 2020 13:14:59 -0800 [thread overview]
Message-ID: <055291a3-265b-be2f-5119-fd7955b8140c@cs.ucla.edu> (raw)
In-Reply-To: <20201228135944.1018303-6-adhemerval.zanella@linaro.org>
On 12/28/20 5:59 AM, Adhemerval Zanella wrote:
> The faccessat (..., AT_EACCESS) on Linux fallback will either use
> __NR_faccessat for __libc_enable_secure or LFS fstatat call. Neither
> fallbacks returns EOVERFLOW in failure case.
Argh, I had misread the glibc source code in this area. So I installed
this further Gnulib patch:
https://git.savannah.gnu.org/cgit/gnulib.git/commit/?id=d82dfeb8a7c9b276c8c7db94d077eb7a43a6760c
which should result in even simpler code than the v2 6/6 patch.
So, to summarize this series of 6 patches to glibc:
* Patches 1, 2, and 3 are fine.
* Patch 4 (stdlib: Sync canonicalize with gnulib) can now sync with
today's Gnulib instead.
* Patch 5 and 6 are no longer needed, since today's Gnulib subsumes them.
next prev parent reply other threads:[~2020-12-28 21:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-28 13:59 [PATCH v2 1/6] Import idx.h from gnulib Adhemerval Zanella
2020-12-28 13:59 ` [PATCH v2 2/6] Import filename.h " Adhemerval Zanella
2020-12-28 13:59 ` [PATCH v2 3/6] malloc: Add scratch_buffer_dupfree Adhemerval Zanella
2020-12-28 13:59 ` [PATCH v2 4/6] stdlib: Sync canonicalize with gnulib [BZ #10635] [BZ #26592] [BZ #26341] [BZ #24970] Adhemerval Zanella
2020-12-28 21:07 ` Paul Eggert
2020-12-28 13:59 ` [PATCH v2 5/6] stdlibc: Simplify realpath via scratch_buffer_dupfree Adhemerval Zanella
2020-12-28 13:59 ` [PATCH v2 6/6] stdlib: Assume FACCESSAT_NEVER_EOVERFLOWS on realpath Adhemerval Zanella
2020-12-28 21:14 ` Paul Eggert [this message]
2020-12-28 21:50 ` Adhemerval Zanella
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
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=055291a3-265b-be2f-5119-fd7955b8140c@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=adhemerval.zanella@linaro.org \
--cc=bug-gnulib@gnu.org \
--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).