diff options
author | David Rientjes <rientjes@google.com> | 2013-04-30 15:28:18 -0700 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2013-04-30 17:04:07 -0700 |
commit | 830e0fc967a7ee5013d5d1cf6a3cea71a8868466 (patch) | |
tree | 19d176024decd5ca10601d2cf2ecc8f0e90fe84e /fs/exec.c | |
parent | dc7ee2aac830e5423f41de87d50441f138f648da (diff) | |
download | linux-stable-830e0fc967a7ee5013d5d1cf6a3cea71a8868466.tar.gz linux-stable-830e0fc967a7ee5013d5d1cf6a3cea71a8868466.tar.bz2 linux-stable-830e0fc967a7ee5013d5d1cf6a3cea71a8868466.zip |
fs, proc: truncate /proc/pid/comm writes to first TASK_COMM_LEN bytes
Currently, a write to a procfs file will return the number of bytes
successfully written. If the actual string is longer than this, the
remainder of the string will not be be written and userspace will
complete the operation by issuing additional write()s.
Hence
$ echo -n "abcdefghijklmnopqrs" > /proc/self/comm
results in
$ cat /proc/$$/comm
pqrs
since the final four bytes were written with a second write() since
TASK_COMM_LEN == 16. This is obviously an undesired result and not
equivalent to prctl(PR_SET_NAME). The implementation should not need to
know the definition of TASK_COMM_LEN.
This patch truncates the string to the first TASK_COMM_LEN bytes and
returns the bytes written as the length of the string written so the
second write() is suppressed.
$ cat /proc/$$/comm
abcdefghijklmno
Signed-off-by: David Rientjes <rientjes@google.com>
Acked-by: John Stultz <john.stultz@linaro.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'fs/exec.c')
0 files changed, 0 insertions, 0 deletions