summaryrefslogtreecommitdiff
path: root/fs/ntfs/upcase.c
diff options
context:
space:
mode:
authorkiyin(尹亮) <kiyin@tencent.com>2020-11-04 08:23:22 +0300
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2020-11-10 12:37:34 +0100
commitb7f7474b392194530d1ec07203c8668e81b7fdb9 (patch)
tree1c9029a0cd6cb99b6856d9ce3ea8d9b4d1a60b2f /fs/ntfs/upcase.c
parent21ab13af8c507b36ccea18d8d1f1c731ee623a9a (diff)
perf/core: Fix a memory leak in perf_event_parse_addr_filter()
commit 7bdb157cdebbf95a1cd94ed2e01b338714075d00 upstream. As shown through runtime testing, the "filename" allocation is not always freed in perf_event_parse_addr_filter(). There are three possible ways that this could happen: - It could be allocated twice on subsequent iterations through the loop, - or leaked on the success path, - or on the failure path. Clean up the code flow to make it obvious that 'filename' is always freed in the reallocation path and in the two return paths as well. We rely on the fact that kfree(NULL) is NOP and filename is initialized with NULL. This fixes the leak. No other side effects expected. [ Dan Carpenter: cleaned up the code flow & added a changelog. ] [ Ingo Molnar: updated the changelog some more. ] Fixes: 375637bc5249 ("perf/core: Introduce address range filtering") Signed-off-by: "kiyin(尹亮)" <kiyin@tencent.com> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com> Signed-off-by: Ingo Molnar <mingo@kernel.org> Cc: "Srivatsa S. Bhat" <srivatsa@csail.mit.edu> Cc: Anthony Liguori <aliguori@amazon.com> -- kernel/events/core.c | 12 +++++------- 1 file changed, 5 insertions(+), 7 deletions(-) Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'fs/ntfs/upcase.c')
0 files changed, 0 insertions, 0 deletions