Date: Thu, 9 Mar 2006 13:58:16 +0100 (CET) From: Anatoli Klassen <dev@26th.net> To: FreeBSD-gnats-submit@FreeBSD.org Subject: kern/94269: procfs shows wrong data if executable is running from nullfs Message-ID: <20060309125816.59E3420C083@26th.net> Resent-Message-ID: <200603091300.k29D0CTd022486@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 94269 >Category: kern >Synopsis: procfs shows wrong data if executable is running from nullfs >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Mar 09 13:00:12 GMT 2006 >Closed-Date: >Last-Modified: >Originator: Anatoli Klassen >Release: FreeBSD 6.1-PRERELEASE i386 >Organization: >Environment: System: FreeBSD pluto 6.1-PRERELEASE FreeBSD 6.1-PRERELEASE #0: Wed Mar 8 23:08:16 CET 2006 root@pluto:/usr/obj/usr/src/sys/PLUTO i386 >Description: I have a nullfs-mounted dir with some executables and a mounted procfs (under /proc). Now if one of the executables tries to read /proc/curproc/file it got an error or sometimes wrong path. >How-To-Repeat: # mount -t procfs procfs /proc # mount -t nullfs /bin /mnt # /bin/ls -l /proc/curproc/file lr--r--r-- 1 root wheel 0 Mar 9 13:53 /proc/curproc/file -> /bin/ls # /mnt/ls -l /proc/curproc/file lr--r--r-- 1 root wheel 0 Mar 9 13:53 /proc/curproc/file -> unknown The second ls shows wrong info. >Fix: >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060309125816.59E3420C083>