mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Fabian Frederick <Fabian.Frederick@skynet.be>
To: Chris Wright <chrisw@osdl.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2.6.5-mm4] sys_access race fix
Date: Tue, 13 Apr 2004 21:12:27 +0200	[thread overview]
Message-ID: <1081883544.5585.30.camel@bluerhyme.real3> (raw)
In-Reply-To: <20040413115052.O22989@build.pdx.osdl.net>

On Tue, 2004-04-13 at 20:50, Chris Wright wrote:
> * Fabian Frederick (Fabian.Frederick@skynet.be) wrote:
> > Andrew,
> > 
> > 	I'm trying to remove the race in sys_access code.
> > AFAICS, fsuid is checked in "permission" level so I pushed real
fsuid
> > capture forward.At that state, I can task_lock (which was impossible
> > before user_walk).Could you tell me if I can improve this one ?
> 
> This changes the semantics of the directory checks implicit
> during the pathname resolution.

Well, the only major function behind user_walk is path_lookup.
This one has some calls with the nameidata.Other process seems
current->fs->xxx relevant read-only.Maybe you mean the
read_lock(&current->fs->lock) which could bring a deadlock as we
task->lock before ? 

If user_walk had to run in ruid, why would we have permission() then ?

Regards,
Fabian

> thanks,
> -chris


  reply	other threads:[~2004-04-13 19:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-13 18:43 Fabian Frederick
2004-04-13 18:50 ` Chris Wright
2004-04-13 19:12   ` Fabian Frederick [this message]
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
2004-04-14  7:22     ` viro
2004-04-14  7:26       ` Jamie Lokier
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=1081883544.5585.30.camel@bluerhyme.real3 \
    --to=fabian.frederick@skynet.be \
    --cc=chrisw@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

all inboxes | Powered by JetHome®