Messages in this thread Patch in this message | | | From | Jiri Slaby <> | Subject | [PATCH 3.12 32/60] fuse: add missing FR_FORCE | Date | Tue, 14 Mar 2017 14:15:23 +0100 |
| |
From: Miklos Szeredi <mszeredi@redhat.com>
3.12-stable review patch. If anyone has any objections, please let me know.
===============
commit 2e38bea99a80eab408adee27f873a188d57b76cb upstream.
fuse_file_put() was missing the "force" flag for the RELEASE request when sending synchronously (fuseblk).
If this flag is not set, then a sync request may be interrupted before it is dequeued by the userspace filesystem. In this case the OPEN won't be balanced with a RELEASE.
[js] force is a variable, not a bit
Signed-off-by: Miklos Szeredi <mszeredi@redhat.com> Fixes: 5a18ec176c93 ("fuse: fix hang of single threaded fuseblk filesystem") Signed-off-by: Jiri Slaby <jslaby@suse.cz> --- fs/fuse/file.c | 1 + 1 file changed, 1 insertion(+)
diff --git a/fs/fuse/file.c b/fs/fuse/file.c index f6314cd3e3b0..75dee32d41b5 100644 --- a/fs/fuse/file.c +++ b/fs/fuse/file.c @@ -128,6 +128,7 @@ static void fuse_file_put(struct fuse_file *ff, bool sync) struct fuse_req *req = ff->reserved_req; if (sync) { + req->force = 1; req->background = 0; fuse_request_send(ff->fc, req); path_put(&req->misc.release.path); -- 2.12.0
| |