[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

/proc/$PID/environ and /proc/$PID/cmdline



Hi!
	Is that normal, that some processes can have strange values in
/proc/$PID/environ and /proc/$PID/cmdline files? Here's the example:

[y4kk0 X ~]$ cat /proc/2089/environ
kk0/klaunchervHCnpc.slave-socket
/tmp/ksocket-y4kk0/kdesktopytHSwa slave-socket[y4kk0 X ~]$
[y4kk0 X ~]$ cat /proc/2089/cmdline
kio_file [kdeinit] file /tmp/ksocket-y4kk0/klaunchervHCnpc.slave-socket
/tmp/ksocket-y4kk0/kdesktopytHSwa.slav
e-socket[y4kk0 X ~]$
[y4kk0 X ~]$ uname -r
2.6.17-1.2647.fc6
[y4kk0 X ~]$ ps aux | grep 2089
y4kk0     2089  0.0  0.9  28060  4844 ?        S    22:14   0:00
kio_file [kdeinit] file /tmp/ksocket-y4kk0/kl
aunchervHCnpc.slave-socket /tmp/ksocket-y4kk0/kdesktopytHSwa.slave-socket
y4kk0     2524  0.0  0.1   3908   756 pts/5    S+   22:24   0:00 grep 2089
[y4kk0 X ~]$

I was told that this is a Fedora's kernel bug. Is that true?

One more thing: I noticed that SELinux blocks access [1] to some files in /proc directory. Some utilities does not know how to handle this situation. For instance `ls -l /proc` run as root shows:

[snip]
-rw-r--r--  1 root      root              0 wrz 16 22:14 mtrr
dr-xr-xr-x  6 root      root              0 wrz 16 22:15 net
-r--r--r--  1 root      root              0 wrz 16 22:26 partitions
?---------  ? ?         ?                 ?            ? /proc/1743
?---------  ? ?         ?                 ?            ? /proc/1759
?---------  ? ?         ?                 ?            ? /proc/1818
?---------  ? ?         ?                 ?            ? /proc/1960
?---------  ? ?         ?                 ?            ? /proc/1965
?---------  ? ?         ?                 ?            ? /proc/1966
?---------  ? ?         ?                 ?            ? /proc/413
-r--r--r--  1 root      root              0 wrz 16 22:26 schedstat
lrwxrwxrwx  1 root      root             64 wrz 16 22:10 self -> 2561
-r--r--r--  1 root      root              0 wrz 16 22:26 slab_allocators
[snip]

Is that a known problem or should I open a bug report?

[1] In permissive mode everything works fine:

[root X ~]# LANG=C ls -l /proc/413
ls: /proc/413: Permission denied
[root X ~]# setenforce 0
[root X ~]# LANG=C ls -l /proc/413
total 0
dr-xr-xr-x 2 root root 0 Sep 16 22:10 attr
-r-------- 1 root root 0 Sep 16 22:10 auxv
-r--r--r-- 1 root root 0 Sep 16 22:10 cmdline
-r--r--r-- 1 root root 0 Sep 16 22:10 cpuset
lrwxrwxrwx 1 root root 0 Sep 16 22:10 cwd -> /
-r-------- 1 root root 0 Sep 16 22:10 environ
lrwxrwxrwx 1 root root 0 Sep 16 22:10 exe -> /sbin/udevd
dr-x------ 2 root root 0 Sep 16 22:10 fd
-rw-r--r-- 1 root root 0 Sep 16 22:10 loginuid
-r-------- 1 root root 0 Sep 16 22:10 maps
-rw------- 1 root root 0 Sep 16 22:10 mem
-r--r--r-- 1 root root 0 Sep 16 22:10 mounts
-r-------- 1 root root 0 Sep 16 22:10 mountstats
-rw-r--r-- 1 root root 0 Sep 16 22:10 oom_adj
-r--r--r-- 1 root root 0 Sep 16 22:10 oom_score
lrwxrwxrwx 1 root root 0 Sep 16 22:10 root -> /
-r--r--r-- 1 root root 0 Sep 16 22:10 schedstat
-r-------- 1 root root 0 Sep 16 22:10 smaps
-r--r--r-- 1 root root 0 Sep 16 22:10 stat
-r--r--r-- 1 root root 0 Sep 16 22:10 statm
-r--r--r-- 1 root root 0 Sep 16 22:10 status
dr-xr-xr-x 3 root root 0 Sep 16 22:10 task
-r--r--r-- 1 root root 0 Sep 16 22:10 wchan
[root X ~]#

Regards,
	Dawid

--

  ^_*


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]