android_kernel_oneplus_msm8998/fs/fuse
Jann Horn a7dfde0f5b fuse: call pipe_buf_release() under pipe lock
commit 9509941e9c534920ccc4771ae70bd6cbbe79df1c upstream.

Some of the pipe_buf_release() handlers seem to assume that the pipe is
locked - in particular, anon_pipe_buf_release() accesses pipe->tmp_page
without taking any extra locks. From a glance through the callers of
pipe_buf_release(), it looks like FUSE is the only one that calls
pipe_buf_release() without having the pipe locked.

This bug should only lead to a memory leak, nothing terrible.

Fixes: dd3bb14f44 ("fuse: support splice() writing to fuse device")
Cc: stable@vger.kernel.org
Signed-off-by: Jann Horn <jannh@google.com>
Signed-off-by: Miklos Szeredi <mszeredi@redhat.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2019-02-20 10:13:16 +01:00
..
control.c fuse: fix control dir setup and teardown 2018-07-03 11:21:28 +02:00
cuse.c fuse: Add reference counting for fuse_io_priv 2016-04-12 09:08:58 -07:00
dev.c fuse: call pipe_buf_release() under pipe lock 2019-02-20 10:13:16 +01:00
dir.c fuse: atomic_o_trunc should truncate pagecache 2018-07-03 11:21:28 +02:00
file.c fuse: Dont call set_page_dirty_lock() for ITER_BVEC pages for async_dio 2018-11-10 07:41:37 -08:00
fuse_i.h fuse: Dont call set_page_dirty_lock() for ITER_BVEC pages for async_dio 2018-11-10 07:41:37 -08:00
inode.c fuse: Fix oops at process_init_reply() 2018-09-05 09:18:39 +02:00
Kconfig fuse: Move CUSE Kconfig entry from fs/Kconfig into fs/fuse/Kconfig 2013-01-17 13:08:45 +01:00
Makefile CUSE: implement CUSE - Character device in Userspace 2009-06-09 11:24:11 +02:00