All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+62e474dd92a35e3060d8@syzkaller.appspotmail.com>
To: alexandr.lobakin@intel.com, andrii@kernel.org, ast@kernel.org,
	bpf@vger.kernel.org, daniel@iogearbox.net, davem@davemloft.net,
	dvyukov@google.com, edumazet@google.com, hawk@kernel.org,
	hdanton@sina.com, jesse.brandeburg@intel.com, joamaki@gmail.com,
	john.fastabend@gmail.com, kafai@fb.com, kpsingh@kernel.org,
	kuba@kernel.org, linux-kernel@vger.kernel.org,
	maximmi@nvidia.com, netdev@vger.kernel.org, pabeni@redhat.com,
	saeedm@nvidia.com, songliubraving@fb.com,
	syzkaller-bugs@googlegroups.com, toke@toke.dk, vladbu@nvidia.com,
	yhs@fb.com
Subject: Re: [syzbot] BUG: corrupted list in netif_napi_add
Date: Mon, 13 Dec 2021 23:52:07 -0800	[thread overview]
Message-ID: <0000000000004e75ca05d316779f@google.com> (raw)
In-Reply-To: <0000000000005639cd05ce3a6d4d@google.com>

syzbot suspects this issue was fixed by commit:

commit 0315a075f1343966ea2d9a085666a88a69ea6a3d
Author: Alexander Lobakin <alexandr.lobakin@intel.com>
Date:   Wed Nov 10 19:56:05 2021 +0000

    net: fix premature exit from NAPI state polling in napi_disable()

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=138dffbeb00000
start commit:   911e3a46fb38 net: phy: Fix unsigned comparison with less t..
git tree:       net-next
kernel config:  https://syzkaller.appspot.com/x/.config?x=d36d2402e8523638
dashboard link: https://syzkaller.appspot.com/bug?extid=62e474dd92a35e3060d8
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=141592f2b00000

If the result looks correct, please mark the issue as fixed by replying with:

#syz fix: net: fix premature exit from NAPI state polling in napi_disable()

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

  parent reply	other threads:[~2021-12-14  7:52 UTC|newest]

Thread overview: 14+ 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
     [not found]       ` <20211023134458.1136-1-hdanton@sina.com>
2021-10-25  6:41         ` Dmitry Vyukov
2021-10-19 10:11     ` Jussi Maki
2021-10-13 14:41 ` Paolo Abeni
2021-12-14  7:52 ` syzbot [this message]
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=0000000000004e75ca05d316779f@google.com \
    --to=syzbot+62e474dd92a35e3060d8@syzkaller.appspotmail.com \
    --cc=alexandr.lobakin@intel.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=dvyukov@google.com \
    --cc=edumazet@google.com \
    --cc=hawk@kernel.org \
    --cc=hdanton@sina.com \
    --cc=jesse.brandeburg@intel.com \
    --cc=joamaki@gmail.com \
    --cc=john.fastabend@gmail.com \
    --cc=kafai@fb.com \
    --cc=kpsingh@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maximmi@nvidia.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=saeedm@nvidia.com \
    --cc=songliubraving@fb.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=toke@toke.dk \
    --cc=vladbu@nvidia.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.