From: syzbot <syzbot+6a3c02010a025ac7b7cf@syzkaller.appspotmail.com>
To: christian@brauner.io, corbet@lwn.net, davem@davemloft.net,
dsahern@gmail.com, dvyukov@google.com, ebiggers@kernel.org,
edumazet@google.com, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
roopa@cumulusnetworks.com, syzkaller-bugs@googlegroups.com,
w.bumiller@proxmox.com
Subject: Re: possible deadlock in neigh_change_state
Date: Sat, 16 Nov 2019 13:58:00 -0800 [thread overview]
Message-ID: <000000000000d9f8a805977dce36@google.com> (raw)
In-Reply-To: <000000000000029056057cd141cb@google.com>
syzbot has bisected this bug to:
commit 58956317c8de52009d1a38a721474c24aef74fe7
Author: David Ahern <dsahern@gmail.com>
Date: Fri Dec 7 20:24:57 2018 +0000
neighbor: Improve garbage collection
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1328a1e2e00000
start commit: addb0679 Merge git://git.kernel.org/pub/scm/linux/kernel/g..
git tree: net-next
final crash: https://syzkaller.appspot.com/x/report.txt?x=10a8a1e2e00000
console output: https://syzkaller.appspot.com/x/log.txt?x=1728a1e2e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=d9655b05acfc97ff
dashboard link: https://syzkaller.appspot.com/bug?extid=6a3c02010a025ac7b7cf
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13317705400000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=177bb01b400000
Reported-by: syzbot+6a3c02010a025ac7b7cf@syzkaller.appspotmail.com
Fixes: 58956317c8de ("neighbor: Improve garbage collection")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2019-11-16 21:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-12 11:11 possible deadlock in neigh_change_state syzbot
2019-11-16 21:58 ` syzbot [this message]
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=000000000000d9f8a805977dce36@google.com \
--to=syzbot+6a3c02010a025ac7b7cf@syzkaller.appspotmail.com \
--cc=christian@brauner.io \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=dvyukov@google.com \
--cc=ebiggers@kernel.org \
--cc=edumazet@google.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=roopa@cumulusnetworks.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=w.bumiller@proxmox.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.