From: syzbot <syzbot+79de6f09efc55fec084b706de3c91e9457433ac5@syzkaller.appspotmail.com>
To: davem@davemloft.net, dccp@vger.kernel.org, dvyukov@google.com,
ebiggers3@gmail.com, gerrit@erg.abdn.ac.uk,
jon.maloy@ericsson.com, kuznet@ms2.inr.ac.ru,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
parthasarathy.bhuvaragan@ericsson.com,
syzkaller-bugs@googlegroups.com,
tipc-discussion@lists.sourceforge.net, ying.xue@windriver.com,
yoshfuji@linux-ipv6.org
Subject: Re: suspicious RCU usage at ./include/net/inet_sock.h:LINE
Date: Thu, 07 Nov 2019 05:42:04 -0800 [thread overview]
Message-ID: <000000000000ac3e9d0596c1d4fe@google.com> (raw)
In-Reply-To: <001a1140ad88c4f006055d3836d2@google.com>
syzbot suspects this bug was fixed by commit:
commit 3f32d0be6c16b902b687453c962d17eea5b8ea19
Author: Parthasarathy Bhuvaragan <parthasarathy.bhuvaragan@ericsson.com>
Date: Tue Sep 25 20:09:10 2018 +0000
tipc: lock wakeup & inputq at tipc_link_reset()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1368cfa2600000
start commit: 464e1d5f
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=bace9f7ec244b823
dashboard link:
https://syzkaller.appspot.com/bug?extid=79de6f09efc55fec084b706de3c91e9457433ac5
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=126079e1800000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=101499e1800000
If the result looks correct, please mark the bug fixed by replying with:
#syz fix: tipc: lock wakeup & inputq at tipc_link_reset()
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2019-11-07 13:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <001a1140ad88c4f006055d3836d2@google.com>
2017-11-05 8:41 ` suspicious RCU usage at ./include/net/inet_sock.h:LINE Dmitry Vyukov
2017-12-26 1:45 ` syzbot
2018-04-08 19:29 ` Eric Biggers
2018-05-17 16:09 ` Dmitry Vyukov
2019-11-07 13:42 ` 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=000000000000ac3e9d0596c1d4fe@google.com \
--to=syzbot+79de6f09efc55fec084b706de3c91e9457433ac5@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=dccp@vger.kernel.org \
--cc=dvyukov@google.com \
--cc=ebiggers3@gmail.com \
--cc=gerrit@erg.abdn.ac.uk \
--cc=jon.maloy@ericsson.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=parthasarathy.bhuvaragan@ericsson.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tipc-discussion@lists.sourceforge.net \
--cc=ying.xue@windriver.com \
--cc=yoshfuji@linux-ipv6.org \
/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).