diff options
| author | Linus Torvalds <[email protected]> | 2025-01-01 19:22:07 +0000 |
|---|---|---|
| committer | Linus Torvalds <[email protected]> | 2025-01-01 19:22:07 +0000 |
| commit | 56e6a3499e14716b9a28a307bb6d18c10e95301e (patch) | |
| tree | efc20c0ec4f68807736e8a049f1d6b2aea5de560 /net/unix/af_unix.c | |
| parent | Merge tag 'platform-drivers-x86-v6.13-4' of git://git.kernel.org/pub/scm/linu... (diff) | |
| parent | tracing: Have process_string() also allow arrays (diff) | |
| download | kernel-56e6a3499e14716b9a28a307bb6d18c10e95301e.tar.gz kernel-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 'net/unix/af_unix.c')
0 files changed, 0 insertions, 0 deletions