summaryrefslogtreecommitdiff
path: root/tools/perf/util/scripting-engines/trace-event-python.c
diff options
context:
space:
mode:
authorMicah Morton <mortonm@chromium.org>2019-09-17 21:27:05 +0300
committerMicah Morton <mortonm@chromium.org>2019-09-17 21:27:05 +0300
commit21ab8580b383f27b7f59b84ac1699cb26d6c3d69 (patch)
tree7d9c05424305e24e211aabdbdd1c5550bcbbc2fb /tools/perf/util/scripting-engines/trace-event-python.c
parent609488bc979f99f805f34e9a32c1e3b71179d10b (diff)
downloadlinux-21ab8580b383f27b7f59b84ac1699cb26d6c3d69.tar.xz
LSM: SafeSetID: Stop releasing uninitialized ruleset
The first time a rule set is configured for SafeSetID, we shouldn't be trying to release the previously configured ruleset, since there isn't one. Currently, the pointer that would point to a previously configured ruleset is uninitialized on first rule set configuration, leading to a crash when we try to call release_ruleset with that pointer. Acked-by: Jann Horn <jannh@google.com> Signed-off-by: Micah Morton <mortonm@chromium.org>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions