From: Olaf Hering <olh@suse.de>
To: linux-kernel@vger.kernel.org
Subject: /bin/ls: cannot read symbolic link /proc/$$/exe: Permission denied
Date: Mon, 16 Aug 2004 15:37:30 +0200 [thread overview]
Message-ID: <20040816133730.GA6463@suse.de> (raw)
For some reasons ls -l /proc/$$/exe doesnt work all time for me,
with 2.6.8.1 on ppc64. Sometimes it does, sometimes not. No pattern.
A few printks show that this check in proc_pid_readlink() triggers
an -EACCES:
current->fsuid != inode->i_uid
proc_pid_readlink(755) error -13 ntptrace(11408) fsuid 100 i_uid 0 0
sys_readlink(281) ntptrace(11408) error -13 readlink
proc_pid_readlink(755) error -13 ls(11509) fsuid 91 i_uid 0 0
sys_readlink(281) ls(11509) error -13 readlink
proc_pid_readlink(755) error -13 ls(11559) fsuid 91 i_uid 0 0
sys_readlink(281) ls(11559) error -13 readlink
proc_pid_readlink(755) error -13 ls(11621) fsuid 91 i_uid 0 0
sys_readlink(281) ls(11621) error -13 readlink
any ideas what is supposed to happen here? Who should set the
inode->i_uid? ssh to the smp box runs the login scripts, they try to
figure out what shell is running via ls -l /proc/$$/exe
This works ok with our 2.6.5 kernel at least.
--
USB is for mice, FireWire is for men!
sUse lINUX ag, nÜRNBERG
next reply other threads:[~2004-08-16 13:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-16 13:37 Olaf Hering [this message]
2004-08-16 22:19 ` /bin/ls: cannot read symbolic link /proc/$$/exe: Permission denied Olaf Hering
2004-08-16 22:39 ` Olaf Hering
2004-08-16 23:34 ` Andreas Schwab
2004-08-17 5:23 ` Olaf Hering
2004-08-17 8:50 ` Andreas Schwab
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=20040816133730.GA6463@suse.de \
--to=olh@suse.de \
--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