summaryrefslogtreecommitdiffstats
path: root/tools/perf/scripts/python/export-to-sqlite.py
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2024-11-03 08:13:52 -1000
committerLinus Torvalds <torvalds@linux-foundation.org>2024-11-03 08:13:52 -1000
commit68f05b251b7156b10a6f6547f7f8672ffb94100f (patch)
tree84df6af460dbcb236442e2b8327cd905f4807498 /tools/perf/scripts/python/export-to-sqlite.py
parent8f0b844adc096feee437c6271a1419ee81383fc6 (diff)
parente3dfd64c1f344ebec9397719244c27b360255855 (diff)
downloadlinux-68f05b251b7156b10a6f6547f7f8672ffb94100f.tar.gz
linux-68f05b251b7156b10a6f6547f7f8672ffb94100f.tar.bz2
linux-68f05b251b7156b10a6f6547f7f8672ffb94100f.zip
Merge tag 'perf-urgent-2024-11-03' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
Pull perf fix from Thomas Gleixner: "perf_event_clear_cpumask() uses list_for_each_entry_rcu() without being in a RCU read side critical section, which triggers a 'suspicious RCU usage' warning. It turns out that the list walk does not be RCU protected because the write side lock is held in this context. Change it to a regular list walk" * tag 'perf-urgent-2024-11-03' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip: perf: Fix missing RCU reader protection in perf_event_clear_cpumask()
Diffstat (limited to 'tools/perf/scripts/python/export-to-sqlite.py')
0 files changed, 0 insertions, 0 deletions