projects / GitHub / LineageOS / android_kernel_motorola_exynos9610.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 545b9fd) | patch
fs: block_dump missing dentry locking
authorNick Piggin <npiggin@suse.de>
Thu, 28 May 2009 07:01:15 +0000 (09:01 +0200)
committerAl Viro <viro@zeniv.linux.org.uk>
Fri, 12 Jun 2009 01:36:10 +0000 (21:36 -0400)
commit4195f73d1329e49727bcceb028e58cb38376c2b0
treeb4c729c164d6907e4186f6dc51e319a604dee416tree | snapshot (tar.gz zip)
parent545b9fd3d737afc0bb5203b1e79194a471605acdcommit | diff
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>
fs/fs-writeback.c diff | blob | blame | history