diff options
| author | Dmitry Vyukov <dvyukov@google.com> | 2018-02-07 00:40:28 +0100 |
|---|---|---|
| committer | Linus Torvalds <torvalds@linux-foundation.org> | 2018-02-07 03:32:46 +0100 |
| commit | a77660d231f8b3d84fd23ed482e0964f7aa546d6 (patch) | |
| tree | de3b60669f8ad14825330b0ec2217bb17bb25d23 /certs/blacklist_nohashes.c | |
| parent | kernel/relay.c: revert "kernel/relay.c: fix potential memory leak" (diff) | |
| download | linux-a77660d231f8b3d84fd23ed482e0964f7aa546d6.tar.xz linux-a77660d231f8b3d84fd23ed482e0964f7aa546d6.zip | |
kcov: detect double association with a single task
Currently KCOV_ENABLE does not check if the current task is already
associated with another kcov descriptor. As the result it is possible
to associate a single task with more than one kcov descriptor, which
later leads to a memory leak of the old descriptor. This relation is
really meant to be one-to-one (task has only one back link).
Extend validation to detect such misuse.
Link: http://lkml.kernel.org/r/20180122082520.15716-1-dvyukov@google.com
Fixes: 5c9a8750a640 ("kernel: add kcov code coverage")
Signed-off-by: Dmitry Vyukov <dvyukov@google.com>
Reported-by: Shankara Pailoor <sp3485@columbia.edu>
Cc: Dmitry Vyukov <dvyukov@google.com>
Cc: syzbot <syzkaller@googlegroups.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'certs/blacklist_nohashes.c')
0 files changed, 0 insertions, 0 deletions