diff options
author | Brian Foster <[email protected]> | 2023-08-31 08:55:00 -0400 |
---|---|---|
committer | Steven Rostedt (Google) <[email protected]> | 2023-09-01 21:26:07 -0400 |
commit | 3d07fa1dd19035eb0b13ae6697efd5caa9033e74 (patch) | |
tree | 81e806fe56119867bc63201156c3a7ff9e62d5bb /lib/test_fortify/write_overflow-strncpy-src.c | |
parent | 2a30dbcbef96f4073d3a5f8708865b1aab0bfc6d (diff) |
tracing: Zero the pipe cpumask on alloc to avoid spurious -EBUSY
The pipe cpumask used to serialize opens between the main and percpu
trace pipes is not zeroed or initialized. This can result in
spurious -EBUSY returns if underlying memory is not fully zeroed.
This has been observed by immediate failure to read the main
trace_pipe file on an otherwise newly booted and idle system:
# cat /sys/kernel/debug/tracing/trace_pipe
cat: /sys/kernel/debug/tracing/trace_pipe: Device or resource busy
Zero the allocation of pipe_cpumask to avoid the problem.
Link: https://lore.kernel.org/linux-trace-kernel/[email protected]
Cc: [email protected]
Fixes: c2489bb7e6be ("tracing: Introduce pipe_cpumask to avoid race on trace_pipes")
Reviewed-by: Zheng Yejian <[email protected]>
Reviewed-by: Masami Hiramatsu (Google) <[email protected]>
Signed-off-by: Brian Foster <[email protected]>
Signed-off-by: Steven Rostedt (Google) <[email protected]>
Diffstat (limited to 'lib/test_fortify/write_overflow-strncpy-src.c')
0 files changed, 0 insertions, 0 deletions