This is the mail archive of the libc-ports@sources.redhat.com mailing list for the libc-ports project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [BUG] Generic syscalls -- chmod vs. fchmodat

From: Arnd Bergmann <arnd at arndb dot de>
To: Roland McGrath <roland at redhat dot com>
Cc: linasvepstas at gmail dot com, Chris Metcalf <cmetcalf at tilera dot com>, GLIBC Devel <libc-alpha at sourceware dot org>, linux-kernel at vger dot kernel dot org, libc-ports at sourceware dot org, linux-api at vger dot kernel dot org, Mike Frysinger <vapier at gentoo dot org>
Date: Tue, 25 Jan 2011 19:21:14 +0100
Subject: Re: [BUG] Generic syscalls -- chmod vs. fchmodat
References: <AANLkTikhKHnR+7DskxYqWXduX4=tpfgsfL4sNYq+4QDq@mail.gmail.com> <201101251529.24779.arnd@arndb.de> <20110125174515.C1DC2183C19@magilla.sf.frob.com>

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.

	Arnd

Follow-Ups:
- Re: [BUG] Generic syscalls -- chmod vs. fchmodat
  - From: Roland McGrath
- Re: [BUG] Generic syscalls -- chmod vs. fchmodat
  - From: Mike Frysinger

References:
- [BUG] Generic syscalls -- chmod vs. fchmodat
  - From: Linas Vepstas
- Re: [BUG] Generic syscalls -- chmod vs. fchmodat
  - From: Arnd Bergmann
- Re: [BUG] Generic syscalls -- chmod vs. fchmodat
  - From: Roland McGrath

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]