Ian Kent e64be33cca autofs4: check kernel communication pipe is valid for write ... It is possible for an autofs mount to become catatonic (and for the daemon communication pipe to become NULL) after a wait has been initiallized but before the request has been sent to the daemon. We need to check for this before sending the request packet. Signed-off-by: Ian Kent <raven@themaw.net> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>		2008-07-24 10:47:32 -07:00
..
autofs_i.h	autofs4: use struct qstr in waitq.c	2008-07-24 10:47:32 -07:00
expire.c	autofs: path_{get,put}() cleanups	2008-05-01 08:04:01 -07:00
init.c	[PATCH] AUTOFS: Make sure all dentries refs are released before calling kill_anon_super()	2006-10-11 11:14:25 -07:00
inode.c	autofs4: fix waitq locking	2008-07-24 10:47:32 -07:00
Makefile
root.c	autofs4: use lookup intent flags to trigger mounts	2008-07-24 10:47:31 -07:00
symlink.c	[PATCH] mark struct inode_operations const 1	2007-02-12 09:48:46 -08:00
waitq.c	autofs4: check kernel communication pipe is valid for write	2008-07-24 10:47:32 -07:00