diff options
author | 2024-08-01 17:43:07 -0700 | |
---|---|---|
committer | 2024-08-15 00:14:48 +0530 | |
commit | 554f07a119866a78606b36123fb28e9451b1f994 (patch) | |
tree | 9382b934c8d2fe6ed4c2a449bbb1242e5d78e912 /tools/perf/scripts/python/call-graph-from-postgresql.py | |
parent | rcuscale: Use special allocator for rcu_scale_writer() (diff) | |
download | wireguard-linux-554f07a119866a78606b36123fb28e9451b1f994.tar.xz wireguard-linux-554f07a119866a78606b36123fb28e9451b1f994.zip |
rcuscale: NULL out top-level pointers to heap memory
Currently, if someone modprobes and rmmods rcuscale successfully, but
the next run errors out during the modprobe, non-NULL pointers to freed
memory will remain. If the run after that also errors out during the
modprobe, there will be double-free bugs.
This commit therefore NULLs out top-level pointers to memory that has
just been freed.
Signed-off-by: "Paul E. McKenney" <paulmck@kernel.org>
Signed-off-by: Neeraj Upadhyay <neeraj.upadhyay@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions