summaryrefslogtreecommitdiffstats
path: root/fs
diff options
context:
space:
mode:
authorNicolai Stange <nicstange@gmail.com>2016-05-24 14:05:05 +0200
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2016-06-15 13:56:35 +0200
commitdf4565f9ebdc4d6dc50edc6e8fed08004e328332 (patch)
tree2acc27591fed42dbe35eb1793bc4e2101b9f3d91 /fs
parentLinux 4.7-rc3 (diff)
downloadlinux-df4565f9ebdc4d6dc50edc6e8fed08004e328332.tar.xz
linux-df4565f9ebdc4d6dc50edc6e8fed08004e328332.zip
kernel/kcov: unproxify debugfs file's fops
Since commit 49d200deaa68 ("debugfs: prevent access to removed files' private data"), a debugfs file's file_operations methods get proxied through lifetime aware wrappers. However, only a certain subset of the file_operations members is supported by debugfs and ->mmap isn't among them -- it appears to be NULL from the VFS layer's perspective. This behaviour breaks the /sys/kernel/debug/kcov file introduced concurrently with commit 5c9a8750a640 ("kernel: add kcov code coverage"). Since that file never gets removed, there is no file removal race and thus, a lifetime checking proxy isn't needed. Avoid the proxying for /sys/kernel/debug/kcov by creating it via debugfs_create_file_unsafe() rather than debugfs_create_file(). Fixes: 49d200deaa68 ("debugfs: prevent access to removed files' private data") Fixes: 5c9a8750a640 ("kernel: add kcov code coverage") Reported-by: Sasha Levin <sasha.levin@oracle.com> Signed-off-by: Nicolai Stange <nicstange@gmail.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'fs')
0 files changed, 0 insertions, 0 deletions