From: Ingo Molnar <mingo@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Jiri Olsa <jolsa@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Mark Rutland <mark.rutland@arm.com>,
Namhyung Kim <namhyung@kernel.org>
Subject: [GIT PULL] perf events fixes
Date: Sun, 15 Nov 2026 13:10:14 +0100 [thread overview]
Message-ID: <avmhJk_EjYcCvAZF@gmail.com> (raw)
Linus,
Please pull the latest perf/urgent Git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git perf-urgent-2026-11-15
for you to fetch changes up to 59f1398140869432c7171b9a2a279ca315467c4e:
Perf events fixes:
- Avoid AMD uncore context migration from non-owners (Sandipan Das)
- Clear stop state in perf_trace_add(), to fix self-profilers
such as async-profiler. Also fix a similar bug in
hw_breakpoint_add(). (Paolo Bertinetti)
- Fix racy update of cpc->hrtimer_interval (Benjamin Segall)
- Do not resurrect cpuctx->cgrp after last cgroup event exit,
to fix UAF bug (Phat Dinh)
Thanks,
Ingo
------------------>
Benjamin Segall (1):
perf: Fix racy update of cpc->hrtimer_interval
Paolo Bertinetti (2):
tracing/perf: Clear stop state in perf_trace_add()
perf/hw_breakpoint: Clear stop state in hw_breakpoint_add()
Phat Dinh (1):
perf/core: Do not resurrect cpuctx->cgrp after last cgroup event exit
Sandipan Das (1):
perf/x86/amd/uncore: Avoid context migration from non-owners
arch/x86/events/amd/uncore.c | 2 +-
kernel/events/core.c | 29 +++++++++++++++++------------
kernel/events/hw_breakpoint.c | 3 +--
kernel/trace/trace_event_perf.c | 3 +--
4 files changed, 20 insertions(+), 17 deletions(-)
next reply other threads:[~2026-11-15 12:10 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-15 12:10 Ingo Molnar [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-11-08 9:09 [GIT PULL] perf events fixes Ingo Molnar
2026-11-08 19:46 ` pr-tracker-bot
2026-10-25 11:11 Ingo Molnar
2026-10-26 3:59 ` pr-tracker-bot
2026-10-18 9:20 Ingo Molnar
2026-10-18 18:15 ` pr-tracker-bot
2026-10-04 7:38 Ingo Molnar
2026-10-04 16:04 ` pr-tracker-bot
2026-09-27 7:59 Ingo Molnar
2026-09-27 19:48 ` pr-tracker-bot
2026-09-20 9:42 Ingo Molnar
2026-09-20 17:21 ` pr-tracker-bot
2026-09-13 8:12 Ingo Molnar
2026-09-13 17:37 ` pr-tracker-bot
2026-09-06 11:13 Ingo Molnar
2026-09-06 18:11 ` pr-tracker-bot
2026-07-11 11:38 Ingo Molnar
2026-07-11 17:14 ` pr-tracker-bot
2026-07-05 7:37 Ingo Molnar
2026-07-05 15:46 ` pr-tracker-bot
2026-05-09 1:40 Ingo Molnar
2026-05-09 3:32 ` pr-tracker-bot
2026-04-12 7:17 Ingo Molnar
2026-04-12 17:45 ` pr-tracker-bot
2026-03-22 8:24 Ingo Molnar
2026-03-22 18:04 ` pr-tracker-bot
2026-03-01 9:00 Ingo Molnar
2026-03-01 21:37 ` pr-tracker-bot
2026-01-24 9:28 Ingo Molnar
2026-01-24 18:00 ` pr-tracker-bot
2025-12-12 9:36 Ingo Molnar
2025-12-13 18:12 ` pr-tracker-bot
2025-11-23 7:45 Ingo Molnar
2025-11-23 16:26 ` pr-tracker-bot
2025-11-01 7:13 Ingo Molnar
2025-11-01 17:41 ` pr-tracker-bot
2025-05-04 7:17 Ingo Molnar
2025-05-04 15:23 ` pr-tracker-bot
2025-04-26 8:35 Ingo Molnar
2025-04-26 17:06 ` pr-tracker-bot
2025-04-18 20:32 Ingo Molnar
2025-04-18 21:15 ` pr-tracker-bot
2025-04-10 21:10 Ingo Molnar
2025-04-10 22:52 ` pr-tracker-bot
2025-03-21 10:39 Ingo Molnar
2025-03-21 17:39 ` pr-tracker-bot
2025-03-07 12:22 Ingo Molnar
2025-03-07 21:04 ` pr-tracker-bot
2025-02-28 19:17 Ingo Molnar
2025-03-01 1:41 ` pr-tracker-bot
2024-06-02 7:08 Ingo Molnar
2024-06-02 16:41 ` pr-tracker-bot
2024-03-17 8:57 Ingo Molnar
2024-03-17 19:34 ` pr-tracker-bot
2023-10-01 8:35 Ingo Molnar
2023-10-01 17:08 ` pr-tracker-bot
2010-09-08 13:00 Ingo Molnar
2010-01-16 16:59 Ingo Molnar
2009-11-10 17:45 Ingo Molnar
2009-11-01 15:36 Ingo Molnar
2009-10-23 14:49 Ingo Molnar
2009-10-13 18:25 Ingo Molnar
2009-10-08 18:37 Ingo Molnar
2009-10-02 12:42 Ingo Molnar
2009-09-26 12:29 Ingo Molnar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=avmhJk_EjYcCvAZF@gmail.com \
--to=mingo@kernel.org \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.