From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 60676] New: Stat system call gives permission denied to root for links under a sticky bit
Date: Thu, 01 Aug 2013 15:02:36 +0000 [thread overview]
Message-ID: <bug-60676-13602@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=60676
Bug ID: 60676
Summary: Stat system call gives permission denied to root for
links under a sticky bit
Product: File System
Version: 2.5
Kernel Version: 3.5.0
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: ext4
Assignee: fs_ext4@kernel-bugs.osdl.org
Reporter: jck@videk.com
Regression: No
If a directory has a sticky bit set, root cannot use anything that makes the
stat system call on any of the links there.
Example:
> $ ls -ld /tmp/
> drwxrwxrwt 17 root root 4825088 Aug 1 10:50 /tmp/
> $ mkdir /tmp/testdir
> $ touch /tmp/testdir/testfile
> $ ln -s /tmp/testdir/ /tmp/testlink
> $ ls /tmp/testlink/
> testfile
> $ su
> # ls /tmp/testlink
ls: cannot access /tmp/testlink: Permission denied
> # ls /tmp/testdir
> testfile
I can see how having root blindly follow links in a sticky directory could be a
bad idea, but this goes against the behavior described by the man pages.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2013-08-01 15:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-01 15:02 bugzilla-daemon [this message]
2013-08-01 15:55 ` [Bug 60676] Stat system call gives permission denied to root for links under a sticky bit bugzilla-daemon
2013-08-01 18:19 ` bugzilla-daemon
2013-08-01 18:21 ` [Bug 60676] New: " Christoph Hellwig
2013-08-02 0:44 ` Theodore Ts'o
2013-08-02 0:44 ` [Bug 60676] " bugzilla-daemon
2013-08-02 3:16 ` jon ernst
2013-08-02 14:34 ` bugzilla-daemon
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=bug-60676-13602@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.