summaryrefslogtreecommitdiff
path: root/arch/mips/include/asm/cpu-features.h
diff options
context:
space:
mode:
authorDaniel Borkmann <daniel@iogearbox.net>2015-11-04 23:33:17 +0100
committerSteven Rostedt <rostedt@goodmis.org>2015-11-04 22:13:45 -0500
commitd227c3ae4e94e5eb11dd780a811f59e1a7b74ccd (patch)
tree1335f64815650b7f1cf7ec457e3453a78bc88a77 /arch/mips/include/asm/cpu-features.h
parent43ed384339ae67a74a8ba4851268b23216ef7a44 (diff)
downloadlinux-d227c3ae4e94e5eb11dd780a811f59e1a7b74ccd.tar.gz
tracefs: Fix refcount imbalance in start_creating()
In tracefs' 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 singleton 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. F.e., in securityfs_create_file(), after doing simple_pin_fs() when lookup_one_len() fails there, we infact do simple_release_fs(). This seems necessary here as well. Same issue seen in debugfs due to 190afd81e4a5 ("debugfs: split the beginning and the end of __create_file() off"), which seemed to got carried over into tracefs, too. Noticed during code review. Link: http://lkml.kernel.org/r/68efa86101b778cf7517ed7c6ad573bd69f60ec6.1446672850.git.daniel@iogearbox.net Fixes: 4282d60689d4 ("tracefs: Add new tracefs file system") Cc: stable@vger.kernel.org # 4.1+ Signed-off-by: Daniel Borkmann <daniel@iogearbox.net> Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
Diffstat (limited to 'arch/mips/include/asm/cpu-features.h')
0 files changed, 0 insertions, 0 deletions