From: Matthew Wilcox <matthew@wil.cx>
To: Oleg Verych <olecom@gmail.com>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: euidaccess() as syscall
Date: Fri, 2 May 2008 11:06:03 -0600 [thread overview]
Message-ID: <20080502170603.GJ14976@parisc-linux.org> (raw)
In-Reply-To: <8499950a0805020959g5114c9c9wa3803a9d1eab3147@mail.gmail.com>
On Fri, May 02, 2008 at 05:59:36PM +0100, Oleg Verych wrote:
> Hallo.
>
> Why there's no euidaccess() syscall (most obvious use is in `test` or
> `[` utility)?
>
> Instead euiaccess() in glibc and access() in kernel are doing unnecessary uid
> shuffling.
Are there any programs which care? Do you have a benchmark that might
show an improvement if we added an euidaccess() syscall?
My impression was that most programs ignore the access() family of
syscalls and just try to do the open and cope with the failure. They
have to anyway, since the file could have changed permission between the
call to access() and the call to open().
--
Intel are signing my paycheques ... these opinions are still mine
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
next prev parent reply other threads:[~2008-05-02 17:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-02 16:59 euidaccess() as syscall Oleg Verych
2008-05-02 17:06 ` Matthew Wilcox [this message]
2008-05-02 17:13 ` Oleg Verych
2008-05-02 17:33 ` Jamie Lokier
2008-05-02 18:45 ` Oleg Verych
2008-05-05 19:21 ` code example (Re: euidaccess() as syscall) Oleg Verych
2008-05-02 17:35 ` euidaccess() as syscall Matthew Wilcox
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=20080502170603.GJ14976@parisc-linux.org \
--to=matthew@wil.cx \
--cc=linux-fsdevel@vger.kernel.org \
--cc=olecom@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 NNTP newsgroup(s).