fs/9p: Compare qid.path in v9fs_test_inode
authorTuomas Tynkkynen <tuomas@tuxera.com>
Wed, 6 Sep 2017 14:59:07 +0000 (17:59 +0300)
committerBen Hutchings <ben@decadent.org.uk>
Tue, 13 Feb 2018 18:32:10 +0000 (18:32 +0000)
commitc37e33929cfaadca634e23e502a8db358ab1babb
tree111c3418bf2991c37c6e3659eb676c7096037d39
parent99dda38c5a7f56cec41af9742f11a137c2279c79
fs/9p: Compare qid.path in v9fs_test_inode

commit 8ee031631546cf2f7859cc69593bd60bbdd70b46 upstream.

Commit fd2421f54423 ("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: fd2421f54423 ("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: Ben Hutchings <ben@decadent.org.uk>
fs/9p/vfs_inode.c
fs/9p/vfs_inode_dotl.c