aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/scripts/gdb/linux/utils.py
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2025-01-01 11:22:07 -0800
committerLinus Torvalds <torvalds@linux-foundation.org>2025-01-01 11:22:07 -0800
commit56e6a3499e14716b9a28a307bb6d18c10e95301e (patch)
treeefc20c0ec4f68807736e8a049f1d6b2aea5de560 /scripts/gdb/linux/utils.py
parentMerge tag 'platform-drivers-x86-v6.13-4' of git://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86 (diff)
parenttracing: Have process_string() also allow arrays (diff)
downloadwireguard-linux-56e6a3499e14716b9a28a307bb6d18c10e95301e.tar.xz
wireguard-linux-56e6a3499e14716b9a28a307bb6d18c10e95301e.zip
Merge tag 'trace-v6.13-rc5' of git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace
Pull tracing fix from Steven Rostedt: "Fix trace event string check when dealing with array of strings The xe_bo_move event has a field that indexes into an array of strings. The TP_fast_assign() added the index into the ring buffer and the TP_printk() had a "%s" that referenced the array using the index in the ring buffer. This is a legitimate use of "%s" in trace events. But this triggered a false positive in the test_event_printk() at boot saying that the string was dangerous. Change the check to allow arrays using fields in the ring buffer as an index to be considered a safe string" * tag 'trace-v6.13-rc5' of git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace: tracing: Have process_string() also allow arrays
Diffstat (limited to 'scripts/gdb/linux/utils.py')
0 files changed, 0 insertions, 0 deletions