| commit | 23d154c71721fd0fa6199851078f32e6bd765664 | |
| author | Miklos Szeredi <mszeredi@suse.cz> | |
| Fri, 25 Feb 2011 13:44:58 +0000 (25 14:44 +0100) | ||
| committer | AK <andi@firstfloor.org> | |
| Thu, 31 Mar 2011 18:58:16 +0000 (31 11:58 -0700) | ||
| tree | 75dc04299727176b916cf3e011babcea9c03e263 | treesnapshot (tar.gz zip) |
| parent | 71f4fa9d7193a64da840be62cc4de3b7e1c6f43c | commitdiff |
fuse: fix hang of single threaded fuseblk filesystem
commit 5a18ec176c934ca1bc9dc61580a5e0e90a9b5733 upstream.
Single threaded NTFS-3G could get stuck if a delayed RELEASE reply
triggered a DESTROY request via path_put().
Fix this by
a) making RELEASE requests synchronous, whenever possible, on fuseblk
filesystems
b) if not possible (triggered by an asynchronous read/write) then do
the path_put() in a separate thread with schedule_work().
Reported-by: Oliver Neukum <oneukum@suse.de>
Signed-off-by: Miklos Szeredi <mszeredi@suse.cz>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Signed-off-by: Andi Kleen <ak@linux.intel.com>
commit 5a18ec176c934ca1bc9dc61580a5e0e90a9b5733 upstream.
Single threaded NTFS-3G could get stuck if a delayed RELEASE reply
triggered a DESTROY request via path_put().
Fix this by
a) making RELEASE requests synchronous, whenever possible, on fuseblk
filesystems
b) if not possible (triggered by an asynchronous read/write) then do
the path_put() in a separate thread with schedule_work().
Reported-by: Oliver Neukum <oneukum@suse.de>
Signed-off-by: Miklos Szeredi <mszeredi@suse.cz>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Signed-off-by: Andi Kleen <ak@linux.intel.com>
| fs/fuse/file.c | diffblobblamehistory | |
| fs/fuse/fuse_i.h | diffblobblamehistory |