diff options
| author | Jann Horn <[email protected]> | 2019-01-12 02:39:05 +0100 |
|---|---|---|
| committer | Miklos Szeredi <[email protected]> | 2019-01-16 10:27:59 +0100 |
| commit | 9509941e9c534920ccc4771ae70bd6cbbe79df1c (patch) | |
| tree | 4b6ee94635855b7826e54c455687a305f0761ff2 /tools/perf/util/scripting-engines/trace-event-python.c | |
| parent | 8a3177db59cd644fde05ba9efee29392dfdec8aa (diff) | |
fuse: call pipe_buf_release() under pipe lock
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: dd3bb14f44a6 ("fuse: support splice() writing to fuse device")
Cc: [email protected]
Signed-off-by: Jann Horn <[email protected]>
Signed-off-by: Miklos Szeredi <[email protected]>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions