Patch "d_walk() might skip too much" has been added to the 3.14-stable tree
Subsystems (2)
This is a note to let you know that I've just added the patch titled
d_walk() might skip too much
to the 3.14-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
d_walk-might-skip-too-much.patch
and it can be found in the queue-3.14 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree, please let <[email protected]> know about it.
Quoted 1 line
From
2159184ea01e4ae7d15f2017e296d4bc82d5aeb0Mon Sep 17 00:00:00 2001
From: Al Viro <[email protected]>
Date: Thu, 28 May 2015 23:09:19 -0400
Subject: d_walk() might skip too much
From: Al Viro <[email protected]>
commit 2159184ea01e4ae7d15f2017e296d4bc82d5aeb0 upstream.
when we find that a child has died while we'd been trying to ascend, we should go into the first live sibling itself, rather than its sibling.
Off-by-one in question had been introduced in "deal with deadlock in d_walk()" and the fix needs to be backported to all branches this one has been backported to.
--- fs/dcache.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)
fs/dcache.c +4 -4
@@ -1135,13 +1135,13 @@ ascend:/* might go back up the wrong parent if we have had a rename. */ if (need_seqretry (&rename_lock, seq)) goto rename_retry; - next = child->d_child.next; -while (unlikely (child->d_flags &DCACHE_DENTRY_KILLED )) { +/* go into the first sibling still alive */ +do { + next = child->d_child.next;if (next == &this_parent->d_subdirs) goto ascend; child = list_entry(next, struct dentry, d_child); - next = next->next; - } + }while (unlikely (child->d_flags &DCACHE_DENTRY_KILLED ));rcu_read_unlock (); goto resume; }
Patches currently in stable-queue which might be from [email protected] are
queue-3.14/d_walk-might-skip-too-much.patch queue-3.14/net-socket-fix-the-wrong-returns-for-recvmsg-and-sendmsg.patch