summaryrefslogtreecommitdiffstats
path: root/fs/proc/meminfo.c
diff options
context:
space:
mode:
authorNeilBrown2018-11-30 00:04:08 +0100
committerJeff Layton2018-11-30 17:26:12 +0100
commitd6367d6241371566597c9ab6efe4de0abf254eed (patch)
tree9c7443570a1cd0bb05d2ddfbcb16b2383851cc35 /fs/proc/meminfo.c
parentocfs2: properly initial file_lock used for unlock. (diff)
downloadkernel-qcow2-linux-d6367d6241371566597c9ab6efe4de0abf254eed.tar.gz
kernel-qcow2-linux-d6367d6241371566597c9ab6efe4de0abf254eed.tar.xz
kernel-qcow2-linux-d6367d6241371566597c9ab6efe4de0abf254eed.zip
fs/locks: use properly initialized file_lock when unlocking.
Both locks_remove_posix() and locks_remove_flock() use a struct file_lock without calling locks_init_lock() on it. This means the various list_heads are not initialized, which will become a problem with a later patch. So change them both to initialize properly. For flock locks, this involves using flock_make_lock(), and changing it to allow a file_lock to be passed in, so memory allocation isn't always needed. Signed-off-by: NeilBrown <neilb@suse.com> Reviewed-by: J. Bruce Fields <bfields@redhat.com> Signed-off-by: Jeff Layton <jlayton@kernel.org>
Diffstat (limited to 'fs/proc/meminfo.c')
0 files changed, 0 insertions, 0 deletions