android_kernel_xiaomi_sm8350/fs/9p
Latchesar Ionkov c959df9f01 v9fs: don't use primary fid when removing file
v9fs_insert uses v9fs_fid_lookup (which also locks the fid) to get the
primary fid associated with the dentry and destroys the v9fs_fid struct
after removing the file.  If another process called v9fs_fid_lookup on the
same dentry, it may wait undefinitely for the fid's lock (as the struct is
freed).

This patch changes v9fs_remove to use a cloned fid, so the primary fid is
not locked and freed.

Signed-off-by: Latchesar Ionkov <lucho@ionkov.net>
Cc: Eric Van Hensbergen <ericvh@hera.kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2007-04-24 08:23:08 -07:00
..
9p.h
conv.c
conv.h
debug.h
error.c
error.h
fcall.c
fcprint.c
fid.c 9p: implement optional loose read cache 2007-02-18 10:16:10 -06:00
fid.h
Makefile
mux.c
mux.h
trans_fd.c
transport.h
v9fs_vfs.h 9p: make struct v9fs_cached_file_operations static 2007-03-26 18:14:44 +00:00
v9fs.c 9p: implement optional loose read cache 2007-02-18 10:16:10 -06:00
v9fs.h 9p: implement optional loose read cache 2007-02-18 10:16:10 -06:00
vfs_addr.c 9p: implement optional loose read cache 2007-02-18 10:16:10 -06:00
vfs_dentry.c 9p: implement optional loose read cache 2007-02-18 10:16:10 -06:00
vfs_dir.c
vfs_file.c 9p: make struct v9fs_cached_file_operations static 2007-03-26 18:14:44 +00:00
vfs_inode.c v9fs: don't use primary fid when removing file 2007-04-24 08:23:08 -07:00
vfs_super.c