From: Paul Jackson <pj@sgi.com>
To: Petr Baudis <pasky@ucw.cz>
Cc: barkalow@iabervon.org, git@vger.kernel.org
Subject: Re: [4/5] Add option for hardlinkable cache of extracted blobs
Date: Sun, 17 Apr 2005 12:25:17 -0700 [thread overview]
Message-ID: <20050417122517.4b12faea.pj@sgi.com> (raw)
In-Reply-To: <20050417174736.GA1461@pasky.ji.cz>
Petr wrote:
> BTW, I'd just use access(F_OK) instead of stat() it I don't care about
That's a bad habit to get into.
access(2) checks with the process's real uid and gid, rather than with
the effective ids as is done when actually attempting an operation.
This is to allow set-UID programs to easily determine the invoking
user's authority.
Using access(2) when it shouldn't be used is a common source of bugs.
I recommend _only_ using it when you require exactly the above real vs.
effective id behaviour.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@engr.sgi.com> 1.650.933.1373, 1.925.600.0401
next prev parent reply other threads:[~2005-04-17 19:23 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050417144947.GG1487@pasky.ji.cz>
2005-04-17 15:20 ` [0/5] Patch set for various things Daniel Barkalow
2005-04-17 15:24 ` [1/5] Parsing code in revision.h Daniel Barkalow
2005-04-17 16:09 ` Petr Baudis
2005-04-17 16:44 ` Daniel Barkalow
2005-04-17 18:18 ` [1/5] " Linus Torvalds
2005-04-17 18:30 ` Petr Baudis
2005-04-17 19:25 ` Linus Torvalds
2005-04-17 19:45 ` Daniel Barkalow
2005-04-17 19:54 ` Linus Torvalds
2005-04-17 20:06 ` Linus Torvalds
2005-04-17 20:22 ` Daniel Barkalow
2005-04-17 19:09 ` Daniel Barkalow
2005-04-17 15:27 ` [2/5] Add merge-base Daniel Barkalow
2005-04-17 16:01 ` Petr Baudis
2005-04-17 16:36 ` Daniel Barkalow
2005-04-17 16:51 ` [2.1/5] " Daniel Barkalow
2005-04-17 21:21 ` Petr Baudis
2005-04-17 21:25 ` Daniel Barkalow
2005-04-17 15:31 ` [3/5] Add http-pull Daniel Barkalow
2005-04-17 18:10 ` Petr Baudis
2005-04-17 18:49 ` Daniel Barkalow
2005-04-17 19:08 ` Petr Baudis
2005-04-17 19:24 ` Daniel Barkalow
2005-04-17 19:59 ` Petr Baudis
2005-04-21 3:27 ` Brad Roberts
2005-04-21 4:28 ` Daniel Barkalow
2005-04-21 22:05 ` tony.luck
2005-04-22 19:46 ` Daniel Barkalow
2005-04-22 22:40 ` Petr Baudis
2005-04-22 23:00 ` Daniel Barkalow
2005-04-22 23:08 ` Petr Baudis
2005-04-22 23:12 ` Daniel Barkalow
2005-04-22 23:24 ` Martin Schlemmer
2005-04-17 18:58 ` [3.1/5] " Daniel Barkalow
2005-04-17 15:35 ` [4/5] Add option for hardlinkable cache of extracted blobs Daniel Barkalow
2005-04-17 17:47 ` Petr Baudis
2005-04-17 18:54 ` Daniel Barkalow
2005-04-17 19:25 ` Paul Jackson [this message]
2005-04-17 19:59 ` Petr Baudis
2005-04-17 20:03 ` Daniel Barkalow
2005-04-17 20:18 ` Petr Baudis
2005-04-18 1:35 ` Paul Jackson
2005-04-18 1:48 ` Petr Baudis
2005-04-18 4:49 ` Paul Jackson
2005-04-17 20:58 ` Russell King
2005-04-17 22:10 ` First ever real kernel git merge! Linus Torvalds
2005-04-18 1:24 ` [4/5] Add option for hardlinkable cache of extracted blobs Paul Jackson
2005-04-18 1:20 ` Paul Jackson
2005-04-17 15:37 ` [5/5] Add commit-id to version Daniel Barkalow
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=20050417122517.4b12faea.pj@sgi.com \
--to=pj@sgi.com \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=pasky@ucw.cz \
/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).