diff options
author | 2010-10-27 21:30:07 -0400 | |
---|---|---|
committer | 2010-10-27 21:30:07 -0400 | |
commit | 4d5476164a052e80d4ef430e368e76dbde96801f (patch) | |
tree | c4949f899392c99896e3e81250c5f667a5ae0ba3 /tools/perf/util/scripting-engines/trace-event-python.c | |
parent | ext4: fix potential infinite loop in ext4_da_writepages() (diff) | |
download | wireguard-linux-4d5476164a052e80d4ef430e368e76dbde96801f.tar.xz wireguard-linux-4d5476164a052e80d4ef430e368e76dbde96801f.zip |
ext4: fix oops in trace_ext4_mb_release_group_pa
Our QA reported an oops in the ext4_mb_release_group_pa tracing,
and Josef Bacik pointed out that it was because we may have a
non-null but uninitialized ac_inode in the allocation context.
I can reproduce it when running xfstests with ext4 tracepoints on,
on a CONFIG_SLAB_DEBUG kernel.
We call trace_ext4_mb_release_group_pa from 2 places,
ext4_mb_discard_group_preallocations and
ext4_mb_discard_lg_preallocations
In both cases we allocate an ac as a container just for tracing (!)
and never fill in the ac_inode. There's no reason to be assigning,
testing, or printing it as far as I can see, so just remove it from
the tracepoint.
Signed-off-by: Eric Sandeen <sandeen@redhat.com>
Reviewed-by: Josef Bacik <josef@redhat.com>
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions