Re: linux-next: manual merge of the bpf-next tree with the bpf tree

From: Alexei Starovoitov

Date: Wed Apr 01 2026 - 11:54:16 EST


On Wed, Apr 1, 2026 at 5:29 AM Mark Brown <broonie@xxxxxxxxxx> wrote:
>
> Hi all,
>
> Today's linux-next merge of the bpf-next tree got a conflict in:
>
> kernel/bpf/verifier.c
>
> between commit:
>
> a8502a79e832b ("bpf: Fix regsafe() for pointers to packet")
>
> from the bpf tree and commit:
>
> 022ac07508836 ("bpf: use reg->var_off instead of reg->off for pointers")
>
> from the bpf-next tree.
>
> I fixed it up (see below) and can carry the fix as necessary. This
> is now fixed as far as linux-next is concerned, but any non trivial
> conflicts should be mentioned to your upstream maintainer when your tree
> is submitted for merging. You may also want to consider cooperating
> with the maintainer of the conflicting tree to minimise any particularly
> complex conflicts.

thanks for headsup.
lgtm
we will get it resolved once bpf tree gets pulled.