autofs: fix lockref lookup
authorIan Kent <raven@themaw.net>
Tue, 6 May 2014 19:50:06 +0000 (12:50 -0700)
committerJiri Slaby <jslaby@suse.cz>
Mon, 9 Jun 2014 13:53:27 +0000 (15:53 +0200)
commitb857b1463899f2e810fff31fe8f775b7e03e9624
treef347dc03ee74412ec4a518247608a7ac96ba9ffa
parent2f1831612c94ee7b1819c4a6d21b9d5efac5297c
autofs: fix lockref lookup

commit 6b6751f7feba68d8f5c72b72cc69a1c5a625529c upstream.

autofs needs to be able to see private data dentry flags for its dentrys
that are being created but not yet hashed and for its dentrys that have
been rmdir()ed but not yet freed.  It needs to do this so it can block
processes in these states until a status has been returned to indicate
the given operation is complete.

It does this by keeping two lists, active and expring, of dentrys in
this state and uses ->d_release() to keep them stable while it checks
the reference count to determine if they should be used.

But with the recent lockref changes dentrys being freed sometimes don't
transition to a reference count of 0 before being freed so autofs can
occassionally use a dentry that is invalid which can lead to a panic.

Signed-off-by: Ian Kent <raven@themaw.net>
Cc: Al Viro <viro@zeniv.linux.org.uk>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Signed-off-by: Jiri Slaby <jslaby@suse.cz>
fs/autofs4/root.c