diff options
author | Linus Torvalds <torvalds@linux-foundation.org> | 2024-10-10 12:25:32 -0700 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2024-10-10 12:25:32 -0700 |
commit | 0edab8d1324dfeee52aad763236c9015e413c4c2 (patch) | |
tree | 178700158c02c7e55c1849266eff4acb623f6ae1 /net | |
parent | eb952c47d154ba2aac794b99c66c3c45eb4cc4ec (diff) | |
parent | 912da2c384d510ce40c5af9c3adc316afa4ec547 (diff) |
Merge tag 'trace-ringbuffer-v6.12-rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace
Pull tracing fix from Steven Rostedt:
"Ring-buffer fix: do not have boot-mapped buffers use CPU hotplug
callbacks
When a ring buffer is mapped to memory assigned at boot, it also
splits it up evenly between the possible CPUs. But the allocation code
still attached a CPU notifier callback to this ring buffer. When a CPU
is added, the callback will happen and another per-cpu buffer is
created for the ring buffer.
But for boot mapped buffers, there is no room to add another one (as
they were all created already). The result of calling the CPU hotplug
notifier on a boot mapped ring buffer is unpredictable and could lead
to a system crash.
If the ring buffer is boot mapped simply do not attach the CPU
notifier to it"
* tag 'trace-ringbuffer-v6.12-rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace:
ring-buffer: Do not have boot mapped buffers hook to CPU hotplug
Diffstat (limited to 'net')
0 files changed, 0 insertions, 0 deletions