aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/dio
diff options
context:
space:
mode:
authorDaniel Borkmann <daniel@iogearbox.net>2015-11-05 00:01:51 +0100
committerAl Viro <viro@zeniv.linux.org.uk>2015-11-11 02:04:44 -0500
commit0ee9608c89e81a1ccee52ecb58a7ff040e2522d9 (patch)
tree97cf1ee6fd2d9e07839529c4fb2befc926ad93f7 /drivers/dio
parentarm64: fixup for mm renames (diff)
downloadlinux-dev-0ee9608c89e81a1ccee52ecb58a7ff040e2522d9.tar.xz
linux-dev-0ee9608c89e81a1ccee52ecb58a7ff040e2522d9.zip
debugfs: fix refcount imbalance in start_creating
In debugfs' start_creating(), we pin the file system to safely access its root. When we failed to create a file, we unpin the file system via failed_creating() to release the mount count and eventually the reference of the vfsmount. However, when we run into an error during lookup_one_len() when still in start_creating(), we only release the parent's mutex but not so the reference on the mount. Looks like it was done in the past, but after splitting portions of __create_file() into start_creating() and end_creating() via 190afd81e4a5 ("debugfs: split the beginning and the end of __create_file() off"), this seemed missed. Noticed during code review. Fixes: 190afd81e4a5 ("debugfs: split the beginning and the end of __create_file() off") Cc: stable@vger.kernel.org # v4.0+ Signed-off-by: Daniel Borkmann <daniel@iogearbox.net> Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Diffstat (limited to 'drivers/dio')
0 files changed, 0 insertions, 0 deletions