From: Mark Brown <broonie@kernel.org>
To: Alan Maguire <alan.maguire@oracle.com>
Cc: peterz@infradead.org, acme@kernel.org, mingo@redhat.com,
namhyung@kernel.org, mark.rutland@arm.com,
alexander.shishkin@linux.intel.com, jolsa@kernel.org,
irogers@google.com, adrian.hunter@intel.com,
james.clark@linaro.org, linux-perf-users@vger.kernel.org,
linux-kernel@vger.kernel.org, bpf@vger.kernel.org
Subject: Re: [PATCH perf] perf: Fix btf_vlen() signedness errors
Date: Mon, 22 Jun 2026 11:53:40 +0100 [thread overview]
Message-ID: <ffdbf003-5f08-4db8-b633-7ed053a738f1@sirena.org.uk> (raw)
In-Reply-To: <20260622103418.579115-1-alan.maguire@oracle.com>
[-- Attachment #1: Type: text/plain, Size: 779 bytes --]
On Mon, Jun 22, 2026 at 11:34:18AM +0100, Alan Maguire wrote:
> Commit f7a6b9eaff3e6 ("bpf: Extend BTF UAPI vlen, kinds to use unused bits")
>
> extended the return value for btf_vlen() to __u32, triggering
> errors for cases where an int was used to store return value.
> Fix these cases for perf as was done for other libbpf consumers.
I already sent:
https://lore.kernel.org/r/20260617130038.34534-1-broonie@kernel.org
which I have been using as a fixup since I originally reported the issue
since Linus' tree is broken, Arnaldo said he'd applied it to the
perf-tools-next branch but it has not yet appeared in Linus' tree (and
it looks like he forgot to push it so his copy isn't getting picked up
in the merge either, the last update was on the 15th).
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 484 bytes --]
next prev parent reply other threads:[~2026-06-22 10:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-22 10:34 Alan Maguire
2026-06-22 10:53 ` Mark Brown [this message]
2026-06-22 11:09 ` Arnaldo Melo
2026-06-22 11:18 ` Mark Brown
2026-06-22 11:31 ` Arnaldo Melo
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=ffdbf003-5f08-4db8-b633-7ed053a738f1@sirena.org.uk \
--to=broonie@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alan.maguire@oracle.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=bpf@vger.kernel.org \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.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®