Chen Jun
467359957a
tracing: Fix a kmemleak false positive in tracing_map ...
[ Upstream commit f25667e5980a4333729cac3101e5de1bb851f71a ]
Doing the command:
echo 'hist:key=common_pid.execname,common_timestamp' > /sys/kernel/debug/tracing/events/xxx/trigger
Triggers many kmemleak reports:
unreferenced object 0xffff0000c7ea4980 (size 128):
comm "bash", pid 338, jiffies 4294912626 (age 9339.324s)
hex dump (first 32 bytes):
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
backtrace:
[<00000000f3469921>] kmem_cache_alloc_trace+0x4c0/0x6f0
[<0000000054ca40c3>] hist_trigger_elt_data_alloc+0x140/0x178
[<00000000633bd154>] tracing_map_init+0x1f8/0x268
[<000000007e814ab9>] event_hist_trigger_func+0xca0/0x1ad0
[<00000000bf8520ed>] trigger_process_regex+0xd4/0x128
[<00000000f549355a>] event_trigger_write+0x7c/0x120
[<00000000b80f898d>] vfs_write+0xc4/0x380
[<00000000823e1055>] ksys_write+0x74/0xf8
[<000000008a9374aa>] __arm64_sys_write+0x24/0x30
[<0000000087124017>] do_el0_svc+0x88/0x1c0
[<00000000efd0dcd1>] el0_svc+0x1c/0x28
[<00000000dbfba9b3>] el0_sync_handler+0x88/0xc0
[<00000000e7399680>] el0_sync+0x148/0x180
unreferenced object 0xffff0000c7ea4980 (size 128):
comm "bash", pid 338, jiffies 4294912626 (age 9339.324s)
hex dump (first 32 bytes):
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
backtrace:
[<00000000f3469921>] kmem_cache_alloc_trace+0x4c0/0x6f0
[<0000000054ca40c3>] hist_trigger_elt_data_alloc+0x140/0x178
[<00000000633bd154>] tracing_map_init+0x1f8/0x268
[<000000007e814ab9>] event_hist_trigger_func+0xca0/0x1ad0
[<00000000bf8520ed>] trigger_process_regex+0xd4/0x128
[<00000000f549355a>] event_trigger_write+0x7c/0x120
[<00000000b80f898d>] vfs_write+0xc4/0x380
[<00000000823e1055>] ksys_write+0x74/0xf8
[<000000008a9374aa>] __arm64_sys_write+0x24/0x30
[<0000000087124017>] do_el0_svc+0x88/0x1c0
[<00000000efd0dcd1>] el0_svc+0x1c/0x28
[<00000000dbfba9b3>] el0_sync_handler+0x88/0xc0
[<00000000e7399680>] el0_sync+0x148/0x180
The reason is elts->pages[i] is alloced by get_zeroed_page.
and kmemleak will not scan the area alloced by get_zeroed_page.
The address stored in elts->pages will be regarded as leaked.
That is, the elts->pages[i] will have pointers loaded onto it as well, and
without telling kmemleak about it, those pointers will look like memory
without a reference.
To fix this, call kmemleak_alloc to tell kmemleak to scan elts->pages[i]
Link: https://lkml.kernel.org/r/20211124140801.87121-1-chenjun102@huawei.com
Signed-off-by: Chen Jun <chenjun102@huawei.com>
Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
Signed-off-by: Sasha Levin <sashal@kernel.org>
2021-12-17 10:12:24 +01:00
2021-09-30 10:09:24 +02:00
2021-07-14 16:53:08 +02:00
2021-02-10 09:25:29 +01:00
2019-08-01 14:16:21 -07:00
2021-10-27 09:54:29 +02:00
2021-01-19 18:26:12 +01:00
2019-07-31 19:03:35 +02:00
2021-07-28 13:31:00 +02:00
2019-04-03 11:02:24 +02:00
2021-06-23 14:41:28 +02:00
2019-10-12 20:44:07 -04:00
2019-08-31 12:19:38 -04:00
2020-10-01 13:17:29 +02:00
2019-10-21 19:38:28 -04:00
2020-01-09 10:20:00 +01:00
2021-11-26 10:47:18 +01:00
2020-06-30 15:37:10 -04:00
2021-12-01 09:23:34 +01:00
2019-07-30 21:50:03 -04:00
2021-10-27 09:54:29 +02:00
2020-12-08 10:40:28 +01:00
2019-05-25 23:04:30 -04:00
2021-09-22 12:26:43 +02:00
2020-10-07 08:01:27 +02:00
2020-10-01 13:18:14 +02:00
2019-10-12 20:48:06 -04:00
2019-05-25 23:04:42 -04:00
2021-09-22 12:26:43 +02:00
2021-09-22 12:26:43 +02:00
2020-02-11 04:35:07 -08:00
2020-01-14 20:08:22 +01:00
2020-11-10 12:37:28 +01:00
2020-01-14 20:08:22 +01:00
2020-02-24 08:36:30 +01:00
2019-04-05 09:26:43 -04:00
2021-12-01 09:23:29 +01:00
2021-07-28 13:31:00 +02:00
2021-12-01 09:23:29 +01:00
2021-12-17 10:12:24 +01:00
467359957a