From: Mike Frysinger <vapier@gentoo.org>
To: Arnd Bergmann <arnd@arndb.de>, Paul Eggert <eggert@cs.ucla.edu>,
Eric Blake <ebb9@byu.net>
Cc: Roland McGrath <roland@redhat.com>,
linasvepstas@gmail.com, Chris Metcalf <cmetcalf@tilera.com>,
GLIBC Devel <libc-alpha@sourceware.org>,
linux-kernel@vger.kernel.org, libc-ports@sourceware.org,
linux-api@vger.kernel.org
Subject: Re: [BUG] Generic syscalls -- chmod vs. fchmodat
Date: Tue, 25 Jan 2011 13:52:00 -0500 [thread overview]
Message-ID: <201101251352.03079.vapier@gentoo.org> (raw)
In-Reply-To: <201101251921.15184.arnd@arndb.de>
[-- Attachment #1: Type: Text/Plain, Size: 926 bytes --]
On Tuesday, January 25, 2011 13:21:14 Arnd Bergmann wrote:
> On Tuesday 25 January 2011 18:45:15 Roland McGrath wrote:
> > I know of no reason to
> >
> > think that the current treatment of the empty string was ever intended at
> > the creation of the *at interfaces.
>
> I always assumed that this was done so that the *at syscalls can replace
> both the ones that take a file descriptor (e.g. fstat) and the ones that
> take a pathname (e.g. stat), which is sensible for the non-AT_FDCWD case,
> although not documented in the man pages.
>
> Treating the empty string special for AT_FDCWD is rather pointless, but
> at least consistent.
i dont know if the gnulib peeps are on these lists, but i think their
implementations of some of the *at funcs leverage the extended behavior that
is available under Linux. or at least, i'm certain they'll have some insight
into some of these nuances.
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2011-01-25 18:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-24 19:57 Linas Vepstas
2011-01-24 21:05 ` Roland McGrath
2011-01-24 21:32 ` Mike Frysinger
2011-01-25 14:29 ` Arnd Bergmann
2011-01-25 17:45 ` Roland McGrath
2011-01-25 18:21 ` Arnd Bergmann
2011-01-25 18:34 ` Roland McGrath
2011-01-25 20:04 ` Arnd Bergmann
2011-01-25 18:52 ` Mike Frysinger [this message]
2011-01-25 19:56 ` Eric Blake
2011-01-25 20:31 ` Eric Blake
2011-01-25 21:32 ` Eric Blake
2011-01-25 22:10 ` Linas Vepstas
2011-02-10 18:12 ` Andries Brouwer
2011-02-10 18:17 ` Roland McGrath
2011-02-11 9:11 ` Andreas Schwab
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=201101251352.03079.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=arnd@arndb.de \
--cc=cmetcalf@tilera.com \
--cc=ebb9@byu.net \
--cc=eggert@cs.ucla.edu \
--cc=libc-alpha@sourceware.org \
--cc=libc-ports@sourceware.org \
--cc=linasvepstas@gmail.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=roland@redhat.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
Powered by JetHome