summaryrefslogtreecommitdiff
path: root/Documentation/input/iforce-protocol.txt
diff options
context:
space:
mode:
authorJeff Layton <jlayton@redhat.com>2016-12-15 13:37:57 (GMT)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2017-10-21 15:21:37 (GMT)
commitbd530852210d9a9bb96cb4c08adc13a6b116c75e (patch)
treeb929752717d18622e5baf9954095f1538a603a1d /Documentation/input/iforce-protocol.txt
parent6839ad59f9d5058b3b7e2c608b4a9d08619134a3 (diff)
downloadlinux-bd530852210d9a9bb96cb4c08adc13a6b116c75e.tar.xz
ceph: clean up unsafe d_parent accesses in build_dentry_path
[ Upstream commit c6b0b656ca24ede6657abb4a2cd910fa9c1879ba ] While we hold a reference to the dentry when build_dentry_path is called, we could end up racing with a rename that changes d_parent. Handle that situation correctly, by using the rcu_read_lock to ensure that the parent dentry and inode stick around long enough to safely check ceph_snap and ceph_ino. Link: http://tracker.ceph.com/issues/18148 Signed-off-by: Jeff Layton <jlayton@redhat.com> Reviewed-by: Yan, Zheng <zyan@redhat.com> Signed-off-by: Ilya Dryomov <idryomov@gmail.com> Signed-off-by: Sasha Levin <alexander.levin@verizon.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'Documentation/input/iforce-protocol.txt')
0 files changed, 0 insertions, 0 deletions