diff options
| author | Eric W. Biederman <[email protected]> | 2008-02-08 12:18:35 +0000 |
|---|---|---|
| committer | Linus Torvalds <[email protected]> | 2008-02-08 17:22:24 +0000 |
| commit | c6caeb7c4544608e8ae62731334661fc396c7f85 (patch) | |
| tree | 3afabe64dedd7bf7d0f88f7612e5f468c8d55c1d /fs/proc/proc_net.c | |
| parent | proc: proper pidns handling for /proc/self (diff) | |
| download | kernel-c6caeb7c4544608e8ae62731334661fc396c7f85.tar.gz kernel-c6caeb7c4544608e8ae62731334661fc396c7f85.zip | |
proc: fix the threaded /proc/self
Long ago when the CLONE_THREAD support first went it someone thought it
would be wise to point /proc/self at /proc/<tgid> instead of /proc/<pid>.
Given that /proc/<tgid> can return information about a very different task
(if enough things have been unshared) then our current process /proc/<tgid>
seems blatantly wrong. So far I have yet to think up an example where the
current behavior would be advantageous, and I can see several places where
it is seriously non-intuitive.
We may be stuck with the current broken behavior for backwards
compatibility reasons but lets try fixing our ancient bug for the 2.6.25
time frame and see if anyone screams.
Signed-off-by: Eric W. Biederman <[email protected]>
Acked-by: Ingo Molnar <[email protected]>
Cc: "Guillaume Chazarain" <[email protected]>
Cc: "Pavel Emelyanov" <[email protected]>
Cc: "Rafael J. Wysocki" <[email protected]>
Cc: Oleg Nesterov <[email protected]>
Cc: Roland McGrath <[email protected]>
Signed-off-by: Andrew Morton <[email protected]>
Signed-off-by: Linus Torvalds <[email protected]>
Diffstat (limited to 'fs/proc/proc_net.c')
0 files changed, 0 insertions, 0 deletions