mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Roland McGrath <roland@redhat.com>
To: linasvepstas@gmail.com
Cc: Chris Metcalf <cmetcalf@tilera.com>,
	Arnd Bergmann <arnd@arndb.de>,
	GLIBC Devel <libc-alpha@sourceware.org>,
	linux-kernel@vger.kernel.org, libc-ports@sourceware.org
Subject: Re: [BUG] Generic syscalls -- chmod vs. fchmodat
Date: Mon, 24 Jan 2011 13:05:14 -0800 (PST)	[thread overview]
Message-ID: <20110124210514.AB18918020B@magilla.sf.frob.com> (raw)
In-Reply-To: Linas Vepstas's message of  Monday, 24 January 2011 13:57:56 -0600 <AANLkTikhKHnR+7DskxYqWXduX4=tpfgsfL4sNYq+4QDq@mail.gmail.com>

POSIX says "A null pathname shall not be successfully resolved."  This
applies to relative pathnames too, and a file name argument to an *at
function using AT_FDCWD is a relative pathname.  So I think there is no
situation at all in which the empty string should resolve to anything.
It's generally in the domain of the kernel to enforce these kinds of rules,
so I think that having the kernel fail with ENOENT for all empty-string
cases is the right thing to do.

Thanks,
Roland

  reply	other threads:[~2011-01-24 21:05 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 [this message]
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
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=20110124210514.AB18918020B@magilla.sf.frob.com \
    --to=roland@redhat.com \
    --cc=arnd@arndb.de \
    --cc=cmetcalf@tilera.com \
    --cc=libc-alpha@sourceware.org \
    --cc=libc-ports@sourceware.org \
    --cc=linasvepstas@gmail.com \
    --cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®