From: syzbot <syzbot+3654c027d861c6df4b06@syzkaller.appspotmail.com>
To: bp@alien8.de, davem@davemloft.net, fweisbec@gmail.com,
hpa@zytor.com, jmaloy@redhat.com, jmattson@google.com,
joro@8bytes.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, mingo@kernel.org, mingo@redhat.com,
pbonzini@redhat.com, sean.j.christopherson@intel.com,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
tuong.t.lien@dektech.com.au, vkuznets@redhat.com,
wanpengli@tencent.com, x86@kernel.org
Subject: Re: INFO: rcu detected stall in tipc_release
Date: Thu, 16 Jul 2020 21:20:04 -0700 [thread overview]
Message-ID: <000000000000a787b205aa9b7863@google.com> (raw)
In-Reply-To: <000000000000264c6305a9c74d9b@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=14641620900000
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=16641620900000
console output: https://syzkaller.appspot.com/x/log.txt?x=12641620900000
kernel config: https://syzkaller.appspot.com/x/.config?x=7be693511b29b338
dashboard link: https://syzkaller.appspot.com/bug?extid=3654c027d861c6df4b06
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12948233100000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11344c05100000
Reported-by: syzbot+3654c027d861c6df4b06@syzkaller.appspotmail.com
Fixes: 5e9eeccc58f3 ("tipc: fix NULL pointer dereference in streaming")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2020-07-17 4:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-06 15:12 INFO: rcu detected stall in tipc_release syzbot
2020-07-17 4:20 ` syzbot [this message]
2020-12-20 9:37 ` syzbot
2020-12-21 9:21 ` Dmitry Vyukov
2020-12-23 10:24 ` 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=000000000000a787b205aa9b7863@google.com \
--to=syzbot+3654c027d861c6df4b06@syzkaller.appspotmail.com \
--cc=bp@alien8.de \
--cc=davem@davemloft.net \
--cc=fweisbec@gmail.com \
--cc=hpa@zytor.com \
--cc=jmaloy@redhat.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=sean.j.christopherson@intel.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=tuong.t.lien@dektech.com.au \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.com \
--cc=x86@kernel.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 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.