From: "Kumar Kartikeya Dwivedi" <memxor@gmail.com>
To: "Paul Moses" <p@1g4.org>, "Kumar Kartikeya Dwivedi" <memxor@gmail.com>
Cc: <martin.lau@linux.dev>, <ast@kernel.org>, <daniel@iogearbox.net>,
<andrii@kernel.org>, <eddyz87@gmail.com>, <bpf@vger.kernel.org>,
<song@kernel.org>, <yonghong.song@linux.dev>, <jolsa@kernel.org>,
<houtao1@huawei.com>, <linux-kernel@vger.kernel.org>,
<stable@vger.kernel.org>
Subject: Re: [PATCH bpf] bpf: Validate BTF repeated field counts before expansion
Date: Sun, 07 Jun 2026 13:08:19 +0200 [thread overview]
Message-ID: <DJ2RQ5NHDCZT.2R218ZSS80NQ4@gmail.com> (raw)
In-Reply-To: <E0xEdilT0Z6figMeDAyw03ex29iX0RfOAUXuh4aTJxUrKHK2Bg5N8lKCHNvQoQQ1UzndFFqDJ_zmAMYHLqSgSfF1menSW7C9VKDSBhYrTT0=@1g4.org>
On Sun Jun 7, 2026 at 12:11 PM CEST, Paul Moses wrote:
>>
>> Do you have an example where this actually occurred in practice?
>>
>
> Yes.
>
Right, I know you can get a splat. But how did you stumble on it? Is this BTF
produced during compilation, or hand-crafted case meant to exercise the limits
such that we get the splat? If you have a small reproducer, it might make sense
to include it as a selftest as well.
> [...]
>
> Also, I still haven't made the connection between the CI failure and
> my patch. I produced what looks like the tcg variation of the same
> failure as a oneoff while testing an (functionally) unpatched kernel.
> I'm not even sure it's the kernel at all and not some weirdness
> between clang and qemu. Seems low frequency intermittent from what
> I've seen so far. Any ideas appreciated.
>
It is unrelated.
next prev parent reply other threads:[~2026-06-07 11:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-05 23:43 [PATCH bpf] bpf: Validate BTF repeated field counts before expansion Paul Moses
2026-06-07 8:59 ` Kumar Kartikeya Dwivedi
2026-06-07 10:11 ` Paul Moses
2026-06-07 11:08 ` Kumar Kartikeya Dwivedi [this message]
2026-06-07 17:53 ` Paul Moses
2026-06-07 16:55 ` Alexei Starovoitov
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=DJ2RQ5NHDCZT.2R218ZSS80NQ4@gmail.com \
--to=memxor@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=houtao1@huawei.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=p@1g4.org \
--cc=song@kernel.org \
--cc=stable@vger.kernel.org \
--cc=yonghong.song@linux.dev \
/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