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, 5 Jul 2026 09:37:36 +0200 [thread overview]
Message-ID: <akoJwHWpTXs6RxUr@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-07-05
for you to fetch changes up to 169328645663bae30e9abad4012d52441e085a71:
Misc perf events fixes:
- Fix a perf_event_attr::remove_on_exec bug for group
events (Taeyang Lee)
- Fix uprobes CALL emulation interaction with shadow stacks,
and add a testcase for this (David Windsor)
- Fix uprobes unregister bug (Jiri Olsa)
Thanks,
Ingo
------------------>
David Windsor (2):
x86/uprobes: Keep shadow stack in sync for emulated CALLs
selftests/x86: Add shadow stack uprobe CALL test
Jiri Olsa (1):
uprobes/x86: Use proper mm_struct in __in_uprobe_trampoline
Taeyang Lee (1):
perf/core: Detach event groups during remove_on_exec
arch/x86/kernel/uprobes.c | 26 +++++---
kernel/events/core.c | 17 ++---
tools/testing/selftests/x86/test_shadow_stack.c | 86 +++++++++++++++++++++++++
3 files changed, 113 insertions(+), 16 deletions(-)
next reply other threads:[~2026-07-05 7:37 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-05 7:37 Ingo Molnar [this message]
2026-07-05 15:46 ` [GIT PULL] perf events fixes pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2026-07-11 11:38 Ingo Molnar
2026-07-11 17:14 ` 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=akoJwHWpTXs6RxUr@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.