From: Kasper Dupont <kasperd@daimi.au.dk>
To: linux-kernel@vger.kernel.org
Subject: Bug in proc permition checks.
Date: Sun, 01 Apr 2001 10:12:25 +0000 [thread overview]
Message-ID: <3AC6FF09.1F7B0A89@daimi.au.dk> (raw)
Somewhere between 2.2.16 and 2.4.1 a bug in
vfs_permission() in the file "fs/namei.c" has
been fixed. S_ISDIR(mode) was incorrect,
S_ISDIR(inode->i_mode) is correct.
The same piece of code exist in the proc
filesystem, here the bug has not been fixed.
I wonder why does the function exist in the
proc filesystem, shouldn't proc be able to
use the default permission cheks?
I have also found a lot of bugs in the file
arch/i386/kernel/vm86.c, this is not mentioned
in the maintainer list. Is there a maintainer
I can send a bug report to? If not I will try
to fix the bugs on my own.
--
Kasper Dupont
reply other threads:[~2001-04-01 10:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3AC6FF09.1F7B0A89@daimi.au.dk \
--to=kasperd@daimi.au.dk \
--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®