There is a complete mess (I haven't figured out why yet) in the way
inode->i_uid/inode->i_gid are handled for the files in /proc/<pid>/ if the
process in question called setuid(2) or setgid(2), i.e. the
proc_pid_fill_inode() is not called on them and thus (? I am not 100% sure
that's the reason) the uid/gid are left to 0/0 (root/root).
This is causing the famous "ps aux|grep login" and then ls -l /proc/<pid>
bug mentioned by Vadim Kogan on #linux this afternoon.
I changed the default for, say "status" to be "500" (tigran) and what I
observe is that it is left to "tigran" which means someone forgot to fill
the inode data, I guess?
This also happens on 2.0.32 which means it's a global and serious problem.
Regards,
------
Tigran A. Aivazian | http://www.sco.com/
Escalations Research Group | Email: tigran@sco.com
Santa Cruz Operation Ltd |
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu