linux-kernel - Re: [syzbot] BUG: corrupted list in netif_napi

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAHn8xcnoPvt4KNZ3cD17PD9qbTa=58h38E8O0zePvYiKHFEc+A@mail.gmail.com>
Date:   Tue, 19 Oct 2021 12:11:28 +0200
From:   Jussi Maki <joamaki@...il.com>
To:     Paolo Abeni <pabeni@...hat.com>
Cc:     Daniel Borkmann <daniel@...earbox.net>,
        syzbot <syzbot+62e474dd92a35e3060d8@...kaller.appspotmail.com>,
        Andrii Nakryiko <andrii@...nel.org>, ast@...nel.org,
        bpf <bpf@...r.kernel.org>, davem@...emloft.net, hawk@...nel.org,
        john.fastabend@...il.com, kafai@...com, kpsingh@...nel.org,
        kuba@...nel.org, linux-kernel@...r.kernel.org,
        Network Development <netdev@...r.kernel.org>,
        songliubraving@...com, syzkaller-bugs@...glegroups.com, yhs@...com,
        toke@...e.dk
Subject: Re: [syzbot] BUG: corrupted list in netif_napi_add

On Thu, Oct 14, 2021 at 3:50 PM Paolo Abeni <pabeni@...hat.com> wrote:
>
> On Wed, 2021-10-13 at 15:35 +0200, Daniel Borkmann wrote:
> > On 10/13/21 1:40 PM, syzbot wrote:
> > > Hello,
> > >
> > > syzbot found the following issue on:
> >
> > [ +Paolo/Toke wrt veth/XDP, +Jussi wrt bond/XDP, please take a look, thanks! ]
>
> For the records: Toke and me are actively investigating this issue and
> the other recent related one. So far we could not find anything
> relevant.
>
> The onluy note is that the reproducer is not extremelly reliable - I
> could not reproduce locally, and multiple syzbot runs on the same code
> give different results. Anyhow, so far the issue was only observerable
> on a specific 'next' commit which is currently "not reachable" from any
> branch. I'm wondering if the issue was caused by some incosistent
> status of such tree.
>

Hey,

I took a look at the bond/XDP related bits and couldn't find anything
obvious there. And for what it's worth, I was running the syzbot repro
under bpf-next tree (223f903e9c8) in the bpf vmtest.sh environment for
30 minutes without hitting this. An inconsistent tree might be a
plausible cause.