Al Viro 9c3e9025a3 cachefiles: vfs_mkdir() might succeed leaving dentry negative unhashed ... That can (and does, on some filesystems) happen - ->mkdir() (and thus vfs_mkdir()) can legitimately leave its argument negative and just unhash it, counting upon the lookup to pick the object we'd created next time we try to look at that name. Some vfs_mkdir() callers forget about that possibility... Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>		2018-05-21 14:30:10 -04:00
..
bind.c	VFS: Convert sb->s_flags & MS_RDONLY to sb_rdonly(sb)	2017-07-17 08:45:34 +01:00
daemon.c	vfs: do bulk POLL* -> EPOLL* replacement	2018-02-11 14:34:03 -08:00
interface.c	fscache: Pass object size in rather than calling back for it	2018-04-06 14:05:14 +01:00
internal.h	fscache: Add tracepoints	2018-04-04 13:41:27 +01:00
Kconfig	CacheFiles: A cache that backs onto a mounted filesystem	2009-04-03 16:42:41 +01:00
key.c	CacheFiles: Downgrade the requirements passed to the allocator	2012-12-20 21:58:25 +00:00
main.c	fscache: Add tracepoints	2018-04-04 13:41:27 +01:00
Makefile	License cleanup: add SPDX GPL-2.0 license identifier to files with no license	2017-11-02 11:10:55 +01:00
namei.c	cachefiles: vfs_mkdir() might succeed leaving dentry negative unhashed	2018-05-21 14:30:10 -04:00
proc.c	drop redundant ->owner initializations	2016-05-29 19:08:00 -04:00
rdwr.c	fscache, cachefiles: Fix checker warnings	2018-04-04 13:41:26 +01:00
security.c	VFS: fs/cachefiles: d_backing_inode() annotations	2015-04-15 15:06:59 -04:00
xattr.c	fscache: Pass object size in rather than calling back for it	2018-04-06 14:05:14 +01:00