diff options
| author | Jeff Layton <jlayton@kernel.org> | 2019-04-15 12:00:42 -0400 |
|---|---|---|
| committer | Ilya Dryomov <idryomov@gmail.com> | 2019-04-23 21:37:54 +0200 |
| commit | 4b8222870032715f9d995f3eb7c7acd8379a275d (patch) | |
| tree | 922907eb1251073439bc094e76800b7f1188c098 /security | |
| parent | 76a495d666e5043ffc315695f8241f5e94a98849 (diff) | |
| download | linux-4b8222870032715f9d995f3eb7c7acd8379a275d.tar.bz2 | |
ceph: handle the case where a dentry has been renamed on outstanding req
It's possible for us to issue a lookup to revalidate a dentry
concurrently with a rename. If done in the right order, then we could
end up processing dentry info in the reply that no longer reflects the
state of the dentry.
If req->r_dentry->d_name differs from the one in the trace, then just
ignore the trace in the reply. We only need to do this however if the
parent's i_rwsem is not held.
Signed-off-by: Jeff Layton <jlayton@kernel.org>
Reviewed-by: "Yan, Zheng" <zyan@redhat.com>
Signed-off-by: Ilya Dryomov <idryomov@gmail.com>
Diffstat (limited to 'security')
0 files changed, 0 insertions, 0 deletions