Tuomas Tynkkynen 8709c53861 fs/9p: Compare qid.path in v9fs_test_inode ... commit 8ee031631546cf2f7859cc69593bd60bbdd70b46 upstream. Commit fd2421f544 ("fs/9p: When doing inode lookup compare qid details and inode mode bits.") transformed v9fs_qid_iget() to use iget5_locked() instead of iget_locked(). However, the test() callback is not checking fid.path at all, which means that a lookup in the inode cache can now accidentally locate a completely wrong inode from the same inode hash bucket if the other fields (qid.type and qid.version) match. Fixes: fd2421f544 ("fs/9p: When doing inode lookup compare qid details and inode mode bits.") Reviewed-by: Latchesar Ionkov <lucho@ionkov.net> Signed-off-by: Tuomas Tynkkynen <tuomas@tuxera.com> Signed-off-by: Al Viro <viro@zeniv.linux.org.uk> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>		2017-11-30 08:37:22 +00:00
..
acl.c
acl.h
cache.c
cache.h
fid.c
fid.h
Kconfig
Makefile
v9fs.c
v9fs.h
v9fs_vfs.h
vfs_addr.c
vfs_dentry.c
vfs_dir.c
vfs_file.c
vfs_inode.c	fs/9p: Compare qid.path in v9fs_test_inode	2017-11-30 08:37:22 +00:00
vfs_inode_dotl.c	fs/9p: Compare qid.path in v9fs_test_inode	2017-11-30 08:37:22 +00:00
vfs_super.c
xattr.c
xattr.h