Mateusz Jurczyk 3abfeac057 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.

Change-Id: Ifcdbf97b5feb73009c4cd152a5f32bd9cce3d3d6
Signed-off-by: Mateusz Jurczyk <mjurczyk@google.com>
Fixes: 37fb3a30b4 ("fuse: fix flock")
Cc: <stable@vger.kernel.org> # v3.1+
Signed-off-by: Miklos Szeredi <mszeredi@redhat.com>
Signed-off-by: Kevin F. Haggerty <haggertk@lineageos.org>

2019-08-08 12:10:17 +02:00

..

control.c

fs: Limit sys_mount to only request filesystem modules.

2019-08-06 10:44:59 +02:00

cuse.c

fs: add module.h to files that were implicitly using it

2011-10-31 19:30:31 -04:00

dev.c

fuse: Add support for d_canonical_path

2019-08-06 10:44:15 +02:00

dir.c

fuse: Add support for d_canonical_path

2019-08-06 10:44:15 +02:00

file.c

fuse: initialize the flock flag in fuse_file on allocation

2019-08-08 12:10:17 +02:00

fuse_i.h

fuse: Add support for d_canonical_path

2019-08-06 10:44:15 +02:00

inode.c

fs: Limit sys_mount to only request filesystem modules.

2019-08-06 10:44:59 +02:00

Kconfig

…

Makefile

…