[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <dca3f426-e3de-207b-51a0-ae272d2b1462@intel.com>
Date: Mon, 20 Mar 2023 13:07:23 +0100
From: Alexander Lobakin <aleksander.lobakin@...el.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>,
Daniel Borkmann <daniel@...earbox.net>,
Alexei Starovoitov <ast@...nel.org>,
Andrii Nakryiko <andrii@...nel.org>
CC: bpf <bpf@...r.kernel.org>, Networking <netdev@...r.kernel.org>,
"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: build failure after merge of the bpf-next tree
From: Stephen Rothwell <sfr@...b.auug.org.au>
Date: Mon, 20 Mar 2023 10:26:19 +1100
> Hi all,
Hi,
>
> After merging the bpf-next tree, today's linux-next build (powerpc
> ppc64_defconfig) failed like this:
>
> net/bpf/test_run.c: In function 'frame_was_changed':
> net/bpf/test_run.c:224:22: error: 'const struct xdp_page_head' has no member named 'frm'; did you mean 'frame'?
> 224 | return head->frm.data != head->orig_ctx.data ||
> | ^~~
> | frame
> net/bpf/test_run.c:225:22: error: 'const struct xdp_page_head' has no member named 'frm'; did you mean 'frame'?
> 225 | head->frm.flags != head->orig_ctx.flags;
> | ^~~
> | frame
The correct solution is to change `frm.` with `frame->`, but I hope the
BPF maintainers will merge bpf into bpf-next to pick up fixes and
changes like this :)
>
> Caused by commit
>
> e5995bc7e2ba ("bpf, test_run: fix crashes due to XDP frame overwriting/corruption")
>
> I have used the bpf-next tree from next-20230317 for today.
>
Thanks,
Olek
Powered by blists - more mailing lists