summaryrefslogtreecommitdiff
path: root/tools/tracing
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2023-02-23 10:08:01 -0800
committerLinus Torvalds <torvalds@linux-foundation.org>2023-02-23 10:08:01 -0800
commit9191423872f764dccc024d6bc4b68dfd138ccc38 (patch)
tree06efe7b39593f8ce2e5347fd9c6c01eea100e2f5 /tools/tracing
parentd392e49ad89059624a2b24daea3c64d0e0fb4124 (diff)
parent8843e06f67b14f71c044bf6267b2387784c7e198 (diff)
Merge tag 'trace-v6.2-rc7-3' of git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace
Pull tracing fix from Steven Rostedt: "Fix race that causes a warning of corrupt ring buffer With the change that allows to read the "trace" file without disabling writing to the ring buffer, there was an integrity check of the ring buffer in the iterator read code, that expected the ring buffer to be write disabled. This caused the integrity check to trigger when stress reading the "trace" file while writing was happening. The integrity check is a bit aggressive (and has never triggered in practice). Change it so that it checks just the integrity of the linked pages without clearing the flags inside the pointers. This removes the warning that was being triggered" [ Heh. This was supposed to have gone in last week before the 6.2 release, but Steven forgot to actually add me to the participants of the pull request, so here it is, a week later - Linus ] * tag 'trace-v6.2-rc7-3' of git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace: ring-buffer: Handle race between rb_move_tail and rb_check_pages
Diffstat (limited to 'tools/tracing')
0 files changed, 0 insertions, 0 deletions