netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jussi Maki <joamaki@gmail.com>
To: Paolo Abeni <pabeni@redhat.com>
Cc: Daniel Borkmann <daniel@iogearbox.net>,
	syzbot <syzbot+62e474dd92a35e3060d8@syzkaller.appspotmail.com>,
	Andrii Nakryiko <andrii@kernel.org>,
	ast@kernel.org, bpf <bpf@vger.kernel.org>,
	davem@davemloft.net, hawk@kernel.org, john.fastabend@gmail.com,
	kafai@fb.com, kpsingh@kernel.org, kuba@kernel.org,
	linux-kernel@vger.kernel.org,
	Network Development <netdev@vger.kernel.org>,
	songliubraving@fb.com, syzkaller-bugs@googlegroups.com,
	yhs@fb.com, toke@toke.dk
Subject: Re: [syzbot] BUG: corrupted list in netif_napi_add
Date: Tue, 19 Oct 2021 12:11:28 +0200	[thread overview]
Message-ID: <CAHn8xcnoPvt4KNZ3cD17PD9qbTa=58h38E8O0zePvYiKHFEc+A@mail.gmail.com> (raw)
In-Reply-To: <f3cc125b2865cce2ea4354b3c93f45c86193545a.camel@redhat.com>

On Thu, Oct 14, 2021 at 3:50 PM Paolo Abeni <pabeni@redhat.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.

  parent reply	other threads:[~2021-10-19 10:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-13 11:40 [syzbot] BUG: corrupted list in netif_napi_add syzbot
2021-10-13 13:35 ` Daniel Borkmann
2021-10-14 13:50   ` Paolo Abeni
2021-10-18 14:04     ` Vlad Buslov
2021-10-18 15:42       ` Jakub Kicinski
2021-10-18 16:12         ` Vlad Buslov
2021-10-18 23:31           ` Saeed Mahameed
2021-10-18 17:40         ` Toke Høiland-Jørgensen
2021-10-18 17:58           ` Jakub Kicinski
2021-10-19 10:11     ` Jussi Maki [this message]
2021-10-13 14:41 ` Paolo Abeni
2021-12-14  7:52 ` syzbot
2021-12-14 17:56   ` Dmitry Vyukov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAHn8xcnoPvt4KNZ3cD17PD9qbTa=58h38E8O0zePvYiKHFEc+A@mail.gmail.com' \
    --to=joamaki@gmail.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=hawk@kernel.org \
    --cc=john.fastabend@gmail.com \
    --cc=kafai@fb.com \
    --cc=kpsingh@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=songliubraving@fb.com \
    --cc=syzbot+62e474dd92a35e3060d8@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=toke@toke.dk \
    --cc=yhs@fb.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).