summaryrefslogtreecommitdiffstats
path: root/fs/jbd
diff options
context:
space:
mode:
authorNick Piggin <npiggin@suse.de>2009-05-28 09:01:15 +0200
committerAl Viro <viro@zeniv.linux.org.uk>2009-06-12 03:36:10 +0200
commit4195f73d1329e49727bcceb028e58cb38376c2b0 (patch)
treeb4c729c164d6907e4186f6dc51e319a604dee416 /fs/jbd
parentfs: remove incorrect I_NEW warnings (diff)
downloadlinux-4195f73d1329e49727bcceb028e58cb38376c2b0.tar.xz
linux-4195f73d1329e49727bcceb028e58cb38376c2b0.zip
fs: block_dump missing dentry locking
I think the block_dump output in __mark_inode_dirty is missing dentry locking. Surely the i_dentry list can change any time, so we may not even *get* a dentry there. If we do get one by chance, then it would appear to be able to go away or get renamed at any time... Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Diffstat (limited to 'fs/jbd')
0 files changed, 0 insertions, 0 deletions