diff options
author | J. Bruce Fields <bfields@citi.umich.edu> | 2007-10-21 16:41:38 -0700 |
---|---|---|
committer | Linus Torvalds <torvalds@woody.linux-foundation.org> | 2007-10-22 08:13:18 -0700 |
commit | 321bcf92163038e2b96fd3bf9bc29f755c81d9ef (patch) | |
tree | 68a1e6b659cac5ffdadb4b7412fa5b7a4244541b /fs/ext2/ext2.h | |
parent | b68680e4731abbd78863063aaa0dca2a6d8cc723 (diff) | |
download | op-kernel-dev-321bcf92163038e2b96fd3bf9bc29f755c81d9ef.zip op-kernel-dev-321bcf92163038e2b96fd3bf9bc29f755c81d9ef.tar.gz |
dcache: don't expose uninitialized memory in /proc/<pid>/fd/<fd>
Well, it's not especially important that target->d_iname get the contents
of dentry->d_iname, but it's important that it get initialized with
*something*, otherwise we're just exposing some random piece of memory to
anyone who reads the link at /proc/<pid>/fd/<fd> for the deleted file, when
it's still held open by someone.
I've run a test program that copies a short (<36 character) name ontop of a
long (>=36 character) name and see that the first time I run it, without
this patch, I get unpredicatable results out of /proc/<pid>/fd/<fd>.
Signed-off-by: J. Bruce Fields <bfields@citi.umich.edu>
Cc: Al Viro <viro@zeniv.linux.org.uk>
Cc: Christoph Hellwig <hch@lst.de>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'fs/ext2/ext2.h')
0 files changed, 0 insertions, 0 deletions