From: Jamie Lokier <jamie@shareable.org>
To: Andrew Morton <akpm@osdl.org>
Cc: Fabian Frederick <Fabian.Frederick@skynet.be>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6.5-mm4] sys_access race fix
Date: Wed, 14 Apr 2004 08:11:02 +0100 [thread overview]
Message-ID: <20040414071102.GB7790@mail.shareable.org> (raw)
In-Reply-To: <20040413170309.14b7a334.akpm@osdl.org>
Andrew Morton wrote:
> Do races in access() actually matter? I mean, some other process could
> change things a nanosecond after access() has completed and the value which
> the access() caller received is wrong anyway.
What about the effect access() has on other callers? It temporarily
changes current->fsuid, so fs operations in other completely
independent threads are affected.
-- Jamie
next prev parent reply other threads:[~2004-04-14 7:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-13 18:43 [PATCH 2.6.5-mm4] sys_access race fix Fabian Frederick
2004-04-13 18:50 ` Chris Wright
2004-04-13 19:12 ` Fabian Frederick
2004-04-13 23:11 ` Chris Wright
2004-04-14 0:03 ` Andrew Morton
2004-04-14 0:16 ` Chris Wright
2004-04-14 7:11 ` Jamie Lokier [this message]
2004-04-14 7:22 ` viro
2004-04-14 7:26 ` Jamie Lokier
-- strict thread matches above, loose matches on Subject: below --
2004-04-14 9:20 fabian.frederick
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=20040414071102.GB7790@mail.shareable.org \
--to=jamie@shareable.org \
--cc=Fabian.Frederick@skynet.be \
--cc=akpm@osdl.org \
--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