From: syzbot <syzbot+4168fa4c45be33afa73c@syzkaller.appspotmail.com>
To: Markus.Elfring@web.de, davem@davemloft.net, fweisbec@gmail.com,
hdanton@sina.com, jmaloy@redhat.com, kuba@kernel.org,
linux-kernel@vger.kernel.org, mingo@kernel.org,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com,
tglx@linutronix.de, tipc-discussion@lists.sourceforge.net,
tuong.t.lien@dektech.com.au, ying.xue@windriver.com
Subject: Re: INFO: rcu detected stall in sock_close (3)
Date: Mon, 20 Jul 2020 00:08:05 -0700 [thread overview]
Message-ID: <00000000000014dc1805aada2bea@google.com> (raw)
In-Reply-To: <0000000000005d946305a9f5d206@google.com>
syzbot has bisected this issue to:
commit 5e9eeccc58f3e6bcc99b929670665d2ce047e9c9
Author: Tuong Lien <tuong.t.lien@dektech.com.au>
Date: Wed Jun 3 05:06:01 2020 +0000
tipc: fix NULL pointer dereference in streaming
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=16c5517d100000
start commit: 7cc2a8ea Merge tag 'block-5.8-2020-07-01' of git://git.ker..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=15c5517d100000
console output: https://syzkaller.appspot.com/x/log.txt?x=11c5517d100000
kernel config: https://syzkaller.appspot.com/x/.config?x=183dd243398ba7ec
dashboard link: https://syzkaller.appspot.com/bug?extid=4168fa4c45be33afa73c
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=112223b7100000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=154793a3100000
Reported-by: syzbot+4168fa4c45be33afa73c@syzkaller.appspotmail.com
Fixes: 5e9eeccc58f3 ("tipc: fix NULL pointer dereference in streaming")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next parent reply other threads:[~2020-07-20 7:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0000000000005d946305a9f5d206@google.com>
2020-07-20 7:08 ` syzbot [this message]
2021-01-15 22:07 ` INFO: rcu detected stall in sock_close (3) syzbot
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=00000000000014dc1805aada2bea@google.com \
--to=syzbot+4168fa4c45be33afa73c@syzkaller.appspotmail.com \
--cc=Markus.Elfring@web.de \
--cc=davem@davemloft.net \
--cc=fweisbec@gmail.com \
--cc=hdanton@sina.com \
--cc=jmaloy@redhat.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=tipc-discussion@lists.sourceforge.net \
--cc=tuong.t.lien@dektech.com.au \
--cc=ying.xue@windriver.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).