[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <cb5d07ac-2224-6ac7-d2b2-cdc5db918106@iogearbox.net>
Date: Wed, 10 Jul 2024 17:16:00 +0200
From: Daniel Borkmann <daniel@...earbox.net>
To: Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
Martin KaFai Lau <martin.lau@...ux.dev>
Cc: syzbot <syzbot+608a2acde8c5a101d07d@...kaller.appspotmail.com>,
netdev@...r.kernel.org, bpf@...r.kernel.org, andrii@...nel.org,
ast@...nel.org, davem@...emloft.net, dsahern@...nel.org, eddyz87@...il.com,
edumazet@...gle.com, haoluo@...gle.com, john.fastabend@...il.com,
jolsa@...nel.org, kpsingh@...nel.org, kuba@...nel.org, pabeni@...hat.com,
sdf@...ichev.me, sdf@...gle.com, song@...nel.org,
syzkaller-bugs@...glegroups.com, yonghong.song@...ux.dev,
Thomas Gleixner <tglx@...utronix.de>, Mathieu Xhonneux
<m.xhonneux@...il.com>, David Lebrun <dlebrun@...gle.com>
Subject: Re: [PATCH bpf-next] bpf: Remove tst_run from lwt_seg6local_prog_ops.
On 7/10/24 4:16 PM, Sebastian Andrzej Siewior wrote:
> The syzbot reported that the lwt_seg6 related BPF ops can be invoked
> via bpf_test_run() without without entering input_action_end_bpf()
> first.
>
> Martin KaFai Lau said that self test for BPF_PROG_TYPE_LWT_SEG6LOCAL
> probably didn't work since it was introduced in commit 04d4b274e2a
> ("ipv6: sr: Add seg6local action End.BPF"). The reason is that the
> per-CPU variable seg6_bpf_srh_states::srh is never assigned in the self
> test case but each BPF function expects it.
>
> Remove test_run for BPF_PROG_TYPE_LWT_SEG6LOCAL.
>
> Suggested-by: Martin KaFai Lau <martin.lau@...ux.dev>
> Reported-by: syzbot+608a2acde8c5a101d07d@...kaller.appspotmail.com
> Fixes: d1542d4ae4df ("seg6: Use nested-BH locking for seg6_bpf_srh_states.")
We can also add in addition for reference:
Fixes: 004d4b274e2a ("ipv6: sr: Add seg6local action End.BPF")
> Signed-off-by: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
Acked-by: Daniel Borkmann <daniel@...earbox.net>
Powered by blists - more mailing lists