https://github.com/torvalds/linux
Revision 4b8222870032715f9d995f3eb7c7acd8379a275d authored by Jeff Layton on 15 April 2019, 16:00:42 UTC, committed by Ilya Dryomov on 23 April 2019, 19:37:54 UTC
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>
1 parent 76a495d
History
Tip revision: 4b8222870032715f9d995f3eb7c7acd8379a275d authored by Jeff Layton on 15 April 2019, 16:00:42 UTC
ceph: handle the case where a dentry has been renamed on outstanding req
Tip revision: 4b82228
File Mode Size
arm
interface
acpi.h -rw-r--r-- 3.4 KB
balloon.h -rw-r--r-- 1.2 KB
events.h -rw-r--r-- 4.3 KB
features.h -rw-r--r-- 502 bytes
grant_table.h -rw-r--r-- 9.7 KB
hvc-console.h -rw-r--r-- 518 bytes
hvm.h -rw-r--r-- 1.3 KB
mem-reservation.h -rw-r--r-- 1.5 KB
page.h -rw-r--r-- 1.3 KB
platform_pci.h -rw-r--r-- 2.0 KB
swiotlb-xen.h -rw-r--r-- 271 bytes
tmem.h -rw-r--r-- 349 bytes
xen-front-pgdir-shbuf.h -rw-r--r-- 2.3 KB
xen-ops.h -rw-r--r-- 8.1 KB
xen.h -rw-r--r-- 1.3 KB
xenbus.h -rw-r--r-- 8.2 KB
xenbus_dev.h -rw-r--r-- 1.8 KB

back to top