On 7/7/22 8:40 PM, Alexei Starovoitov wrote:
On Thu, Jul 7, 2022 at 11:36 AM Eric Dumazet <edumazet@xxxxxxxxxx> wrote:
On Thu, Jul 7, 2022 at 8:31 PM Alexei Starovoitov
<alexei.starovoitov@xxxxxxxxx> wrote:
On Thu, Jul 7, 2022 at 11:20 AM <patchwork-bot+netdevbpf@xxxxxxxxxx> wrote:
Hello:
This patch was applied to bpf/bpf.git (master)
Are we sure it's bpf tree material?
The fixes tag points to net-next tree.
Fix is generic and should not harm bpf tree, or any tree if that matters.
Right. Just trying to understand the urgency/severity
considering we're at rc5.
The Fixes tag points to the warning that has been added. I understand more
as a reference rather than the actual underlying bug that syzkaller was
able to trigger w/ classic bpf. So yeah, bpf tree seems reasonable, imho,
but also low risk from patch diff itself.
Thanks,
Daniel
