LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Vegard Nossum" <firstname.lastname@example.org>
To: "Eric W. Biederman" <email@example.com>,
"Al Viro" <firstname.lastname@example.org>
Cc: "Rafael J. Wysocki" <email@example.com>,
"Alexey Dobriyan" <firstname.lastname@example.org>,
"Ingo Molnar" <email@example.com>,
"Pekka Enberg" <firstname.lastname@example.org>,
LKML <email@example.com>, "Greg KH" <firstname.lastname@example.org>,
"Kay Sievers" <email@example.com>,
Subject: Re: v2.6.28-rc1: readlink /proc/*/exe returns uninitialized data to userspace
Date: Sun, 26 Oct 2008 22:08:45 +0100 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
[Combined result for Eric & Viro]
On Sat, Oct 25, 2008 at 11:28 PM, Eric W. Biederman
>> On Saturday, 25 of October 2008, Vegard Nossum wrote:
>>> When I run readlink on the /proc/*/exe-file for udevd, the kernel
>>> returns some unitialized data to userspace:
>>> # strace -e trace=readlink readlink /proc/4762/exe
>>> readlink("/proc/4762/exe", "/sbin/udevd", 1025) = 30
>>> You can see it because the kernel thinks that the string is 30 bytes
>>> long, but in fact it is only 12 (including the '\0').
> Weird. The dentry for "udevd" has an incorrect length.
> Is something stomping the length somewhere?
> What filesystem does /sbin/udevd reside on?
Ext3 on a USB flash-disk.
On Sun, Oct 26, 2008 at 1:23 AM, Al Viro <email@example.com> wrote:
>> (For the record: This didn't show up in 2.6.27-rc with the same
>> version of LTP, so it seems to be a recent regression.)
> Very odd. Do you see that for any other processes? Where does
> /sbin/udevd live on your box? BTW, .config might be useful here...
> Can you reproduce that on e.g. amd64 and/or without kmemcheck?
IIRC, it did show up for other processes, but udevd was the only one
which exhibited the problem reliably.
Now, I've been trying to reproduce the problem (with exact same setup)
since I first saw it, but can't :-/ At the time that the machine
started showing the problem, it had been running LTP, scrashme, etc.
for hours, so it seems that it might have had something to do with it.
I couldn't reproduce it after rebooting.
This was my setup:
- root filesystem (ext3) on USB flash disk
- mounted LVM2/ext3 from harddisk on /mnt
- bind-mounted /proc onto /mnt/proc
I noticed the problem from chroot /mnt, but it reproduced afterwards
on the outside as well. I also remember having remounted (with -o
remount) both /mnt (adding user_xattr to options) and /mnt/proc from
within the chroot (so with /mnt prefix removed). This could of course
all be unrelated since it didn't reproduce the problem, but at least
it is what I did.
Cosmic rays may have been involved. Will keep trying to reproduce.
Thanks for attention so far.
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
-- E. W. Dijkstra, EWD1036
next prev parent reply other threads:[~2008-10-26 21:08 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-25 17:14 Vegard Nossum
2008-10-25 20:41 ` Rafael J. Wysocki
2008-10-25 22:28 ` Eric W. Biederman
2008-10-26 21:08 ` Vegard Nossum [this message]
2008-11-04 9:39 ` Vegard Nossum
2008-11-04 10:00 ` Alexey Dobriyan
2008-11-04 10:07 ` Alexey Dobriyan
2008-11-04 10:34 ` Alexey Dobriyan
2008-11-04 10:54 ` Eric W. Biederman
2008-11-04 15:48 ` Al Viro
2008-11-04 15:12 ` Al Viro
2008-11-06 10:04 ` Ingo Molnar
2008-11-07 19:05 ` Greg KH
2008-11-07 23:12 ` Alexey Dobriyan
2008-11-11 22:14 ` Andrew Morton
2008-11-11 22:53 ` Vegard Nossum
2008-12-03 17:18 ` Greg KH
2008-12-03 20:20 ` Andrew Morton
2008-12-07 5:44 ` Greg KH
2008-12-07 7:04 ` Al Viro
2008-10-26 0:23 ` Al Viro
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--subject='Re: v2.6.28-rc1: readlink /proc/*/exe returns uninitialized data to userspace' \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).