From: Paul Larson <plars@austin.ibm.com>
To: Alexander Viro <viro@math.psu.edu>
Cc: Bob_Tracy <rct@gherkin.frus.com>,
system_lists@nullzone.org, linux-kernel@vger.kernel.org
Subject: Re: SEVERE Problems in 2.5.12 at uid0 access
Date: 02 May 2002 16:39:01 -0500 [thread overview]
Message-ID: <1020375541.3862.20.camel@plars.austin.ibm.com> (raw)
In-Reply-To: <Pine.GSO.4.21.0205011417230.12640-100000@weyl.math.psu.edu>
On Wed, 2002-05-01 at 13:18, Alexander Viro wrote:
> Yes, it is. Look for the patch I've posted yesterday (subject was
> something like "[PATCH] missing checks", IIRC).
Before I found this message I was also trying to hunt down this problem
after noticing that 2.5.12 failed unlink08 from LTP. The thing I think
broke it though was a seemlingly minor change to the handling of the
return value from exec_permission_lite in link_path_walk(). In 2.5.11
it rechecked with permission() if it got an error back from
exec_permission_lite(), but in 2.5.12 it only does this if err ==
-EAGAIN. This patch also seems to fix the problem, and simply reverts
it back to the original way it was handled rather than adding more code
to exec_permission_lite(). I'll let you decide which is the best way.
Thanks,
Paul Larson
--- linux/fs/namei.c Thu May 2 18:36:01 2002
+++ linux-fix/fs/namei.c Thu May 2 18:36:17 2002
@@ -573,7 +573,7 @@
unsigned int c;
err = exec_permission_lite(inode);
- if (err == -EAGAIN) {
+ if (err) {
unlock_nd(nd);
err = permission(inode, MAY_EXEC);
lock_nd(nd);
next prev parent reply other threads:[~2002-05-02 21:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-01 11:14 system_lists
2002-05-01 17:06 ` Bob_Tracy
2002-05-01 17:56 ` Pierre Rousselet
2002-05-01 18:04 ` Bob_Tracy
2002-05-01 18:13 ` Skip Ford
2002-05-01 18:18 ` Alexander Viro
2002-05-02 21:39 ` Paul Larson [this message]
[not found] <Pine.GSO.4.21.0205011417230.12640-100000@weyl.math.psu.edu >
2002-05-01 18:57 ` system_lists
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=1020375541.3862.20.camel@plars.austin.ibm.com \
--to=plars@austin.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rct@gherkin.frus.com \
--cc=system_lists@nullzone.org \
--cc=viro@math.psu.edu \
/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®