diff options
author | Mateusz Jurczyk <mjurczyk@google.com> | 2017-06-07 12:26:49 +0200 |
---|---|---|
committer | Miklos Szeredi <mszeredi@redhat.com> | 2017-06-09 11:16:22 +0200 |
commit | 68227c03cba84a24faf8a7277d2b1a03c8959c2c (patch) | |
tree | 3f477053fd341d1a14da8b1e9408bdd2559c6c03 /fs/fuse/control.c | |
parent | 2ea659a9ef488125eb46da6eb571de5eae5c43f6 (diff) | |
download | linux-rt-68227c03cba84a24faf8a7277d2b1a03c8959c2c.tar.gz |
fuse: initialize the flock flag in fuse_file on allocation
Before the patch, the flock flag could remain uninitialized for the
lifespan of the fuse_file allocation. Unless set to true in
fuse_file_flock(), it would remain in an indeterminate state until read in
an if statement in fuse_release_common(). This could consequently lead to
taking an unexpected branch in the code.
The bug was discovered by a runtime instrumentation designed to detect use
of uninitialized memory in the kernel.
Signed-off-by: Mateusz Jurczyk <mjurczyk@google.com>
Fixes: 37fb3a30b462 ("fuse: fix flock")
Cc: <stable@vger.kernel.org> # v3.1+
Signed-off-by: Miklos Szeredi <mszeredi@redhat.com>
Diffstat (limited to 'fs/fuse/control.c')
0 files changed, 0 insertions, 0 deletions