ring-buffer: Do not poll non allocated cpu buffers
The tracing infrastructure sets up for possible CPUs, but it uses the ring buffer polling, it is possible to call the ring buffer polling code with a CPU that hasn't been allocated. This will cause a kernel oops when it access a ring buffer cpu buffer that is part of the possible cpus but hasn't been allocated yet as the CPU has never been online. Reported-by:Mauro Carvalho Chehab <mchehab@redhat.com> Tested-by:
Mauro Carvalho Chehab <mchehab@redhat.com> Signed-off-by:
Steven Rostedt <rostedt@goodmis.org>
parent
ca164318
Please register or sign in to comment