| commit | 5c46eb076e0a1b2c1769287cd6942e4594ade1b1 | |
| author | Miklos Szeredi <mszeredi@suse.cz> | |
| Fri, 25 Feb 2011 13:44:58 +0000 (25 14:44 +0100) | ||
| committer | Greg Kroah-Hartman <gregkh@suse.de> | |
| Mon, 21 Mar 2011 19:45:24 +0000 (21 12:45 -0700) | ||
| tree | 1fb646ff1636d1e1b5fef48e673dd7ead255f71e | treesnapshot (tar.gz zip) |
| parent | 4389b6188647b4dbc84d54bbc467ddf966dcb837 | 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>
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>
| fs/fuse/file.c | diffblobblamehistory | |
| fs/fuse/fuse_i.h | diffblobblamehistory |