From: Namhyung Kim <namhyung@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
Ian Rogers <irogers@google.com>,
Kan Liang <kan.liang@linux.intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-perf-users@vger.kernel.org
Subject: [GIT PULL] perf-tools fixes for v6.17-rc5
Date: Fri, 5 Sep 2025 13:20:12 -0700 [thread overview]
Message-ID: <20250905202012.2341155-1-namhyung@kernel.org> (raw)
Hi Linus,
Please consider pulling the following changes in perf tools for v6.17.
This includes fixes for segfaults that I reported earlier.
Thanks,
Namhyung
The following changes since commit 2c369d91d0933aaff96b6b807b22363e6a38a625:
perf symbol: Add blocking argument to filename__read_build_id (2025-08-25 15:07:18 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/perf/perf-tools.git tags/perf-tools-fixes-for-v6.17-2025-09-05
for you to fetch changes up to ca81e74dc34734078d34485d4aa123561ba75b15:
perf symbol-elf: Add support for the block argument for libbfd (2025-09-04 16:37:35 -0700)
----------------------------------------------------------------
perf-tools fixes for v6.17-rc5
This series contains fixes for use-after-free resulted in segfaults
after merging the bpf tree. Also a couple of build and test fixes.
Signed-off-by: Namhyung Kim <namhyung@kernel.org>
----------------------------------------------------------------
Ian Rogers (4):
perf bpf-event: Fix use-after-free in synthesis
perf bpf-utils: Constify bpil_array_desc
perf bpf-utils: Harden get_bpf_prog_info_linear
perf symbol-elf: Add support for the block argument for libbfd
James Clark (1):
perf tests: Fix "PE file support" test build
Thomas Richter (1):
perf test: Checking BPF metadata collection fails on version string
tools/perf/tests/pe-file-parsing.c | 4 +-
tools/perf/tests/shell/test_bpf_metadata.sh | 2 +-
tools/perf/util/bpf-event.c | 39 ++++++++++++------
tools/perf/util/bpf-utils.c | 61 ++++++++++++++++++-----------
tools/perf/util/symbol-elf.c | 10 +++--
5 files changed, 76 insertions(+), 40 deletions(-)
next reply other threads:[~2025-09-05 20:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-05 20:20 Namhyung Kim [this message]
2025-09-05 22:34 ` pr-tracker-bot
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=20250905202012.2341155-1-namhyung@kernel.org \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=irogers@google.com \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®