From: syzbot <syzbot+47bbc6b678d317cccbe0@syzkaller.appspotmail.com>
To: arnd@arndb.de, davem@davemloft.net, gregkh@linuxfoundation.org,
jarkko.sakkinen@linux.intel.com, jgg@ziepe.ca, jmaloy@redhat.com,
jsnitsel@redhat.com, kuba@kernel.org,
linux-integrity@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, peterhuewe@gmx.de,
syzkaller-bugs@googlegroups.com,
tipc-discussion@lists.sourceforge.net, ying.xue@windriver.com
Subject: Re: WARNING: suspicious RCU usage in tipc_l2_send_msg
Date: Wed, 12 Aug 2020 04:53:05 -0700 [thread overview]
Message-ID: <000000000000aae24a05acacd485@google.com> (raw)
In-Reply-To: <000000000000d411cf05a8ffc4a6@google.com>
syzbot has bisected this issue to:
commit 786a2aa281f4c4ba424ea8b8ea1e85ab62c4a57c
Author: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
Date: Mon Jul 6 20:53:42 2020 +0000
Revert commit e918e570415c ("tpm_tis: Remove the HID IFX0102")
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=12fc36d6900000
start commit: 4437dd6e Merge tag 'io_uring-5.8-2020-07-12' of git://git...
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=11fc36d6900000
console output: https://syzkaller.appspot.com/x/log.txt?x=16fc36d6900000
kernel config: https://syzkaller.appspot.com/x/.config?x=66ad203c2bb6d8b
dashboard link: https://syzkaller.appspot.com/bug?extid=47bbc6b678d317cccbe0
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10c005af100000
Reported-by: syzbot+47bbc6b678d317cccbe0@syzkaller.appspotmail.com
Fixes: 786a2aa281f4 ("Revert commit e918e570415c ("tpm_tis: Remove the HID IFX0102")")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2020-08-12 11:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-26 17:09 WARNING: suspicious RCU usage in tipc_l2_send_msg syzbot
2020-07-13 8:05 ` syzbot
2020-08-12 11:53 ` syzbot [this message]
2020-08-19 9:09 ` Xin Long
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=000000000000aae24a05acacd485@google.com \
--to=syzbot+47bbc6b678d317cccbe0@syzkaller.appspotmail.com \
--cc=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=jgg@ziepe.ca \
--cc=jmaloy@redhat.com \
--cc=jsnitsel@redhat.com \
--cc=kuba@kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=peterhuewe@gmx.de \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tipc-discussion@lists.sourceforge.net \
--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 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.