From: Greg KH <greg@kroah.com>
To: Lorenz Bauer <lmb@isovalent.com>
Cc: stable@vger.kernel.org
Subject: Re: linux-5.10.y: please backport to fix BPF selftest breakage
Date: Sun, 16 Jul 2023 17:18:54 +0200 [thread overview]
Message-ID: <2023071647-retiring-embroider-2e33@gregkh> (raw)
In-Reply-To: <CAN+4W8j6G4f9Pg+rb+gcO06OU8ovudhbwXj0+E8Gg09zrozcZQ@mail.gmail.com>
On Wed, Jul 12, 2023 at 10:40:32AM +0100, Lorenz Bauer wrote:
> Hi stable team,
>
> Building BPF selftests on 5.10.186 currently causes the following compile error:
>
> $ make -C tools/testing/selftests/bpf
> ...
> BINARY test_verifier
> In file included from
> /usr/src/linux-5.10.186/tools/testing/selftests/bpf/verifier/tests.h:59,
> from test_verifier.c:355:
> /usr/src/linux-5.10.186/tools/testing/selftests/bpf/verifier/ref_tracking.c:935:10:
> error: 'struct bpf_test' has no member named 'fixup_map_ringbuf'; did
> you mean 'fixup_map_in_map'?
> 935 | .fixup_map_ringbuf = { 11 },
> | ^~~~~~~~~~~~~~~~~
> | fixup_map_in_map
>
> The problem was introduced by commit f4b8c0710ab6 ("selftests/bpf: Add
> verifier test for release_reference()") in your tree.
>
> Seems like at least commit 4237e9f4a962 ("selftests/bpf: Add verifier
> test for PTR_TO_MEM spill") is required for the build to succeed.
>
> I previously reported this but things probably fell through the
> cracks: https://lore.kernel.org/stable/CAN+4W8iMcwwVjmSekZ9txzZNxOZ0x98nBXo4cEoTU9G2zLe8HA@mail.gmail.com/#t
Now queued up, thanks.
greg k-h
prev parent reply other threads:[~2023-07-16 15:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 9:40 linux-5.10.y: please backport to fix BPF selftest breakage Lorenz Bauer
2023-07-16 15:18 ` Greg KH [this message]
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=2023071647-retiring-embroider-2e33@gregkh \
--to=greg@kroah.com \
--cc=lmb@isovalent.com \
--cc=stable@vger.kernel.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