From: Greg KH <greg@kroah.com>
To: syzbot <syzbot+42bc0d31b9a21faebdf8@syzkaller.appspotmail.com>
Cc: andreyknvl@google.com, bp@alien8.de, devel@etsukata.com,
hpa@zytor.com, linux-kernel@vger.kernel.org,
linux-usb@vger.kernel.org, mingo@redhat.com,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
viro@zeniv.linux.org.uk, x86@kernel.org
Subject: Re: INFO: trying to register non-static key in is_dynamic_key
Date: Fri, 19 Jun 2020 09:05:27 +0200 [thread overview]
Message-ID: <20200619070527.GA544353@kroah.com> (raw)
In-Reply-To: <00000000000004a76305a8624d22@google.com>
On Thu, Jun 18, 2020 at 02:17:15PM -0700, syzbot wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit: b791d1bd Merge tag 'locking-kcsan-2020-06-11' of git://git..
> git tree: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git usb-testing
> console output: https://syzkaller.appspot.com/x/log.txt?x=13f305a9100000
> kernel config: https://syzkaller.appspot.com/x/.config?x=16c2467d4b6dbee2
> dashboard link: https://syzkaller.appspot.com/bug?extid=42bc0d31b9a21faebdf8
> compiler: gcc (GCC) 9.0.0 20181231 (experimental)
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=136ad566100000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10138f7a100000
>
> IMPORTANT: if you fix the bug, please add the following tag to the commit:
> Reported-by: syzbot+42bc0d31b9a21faebdf8@syzkaller.appspotmail.com
>
> INFO: trying to register non-static key.
> the code is fine but needs lockdep annotation.
Why is INFO: triggering syzbot?
next prev parent reply other threads:[~2020-06-19 7:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-18 21:17 INFO: trying to register non-static key in is_dynamic_key syzbot
2020-06-19 7:05 ` Greg KH [this message]
2020-06-19 7:35 ` Dmitry Vyukov
2020-06-19 7:47 ` Greg KH
2020-06-19 9:11 ` Dmitry Vyukov
2020-06-19 9:53 ` Peter Zijlstra
2020-06-19 10:03 ` Dmitry Vyukov
2020-06-19 13:39 ` Andrey Konovalov
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=20200619070527.GA544353@kroah.com \
--to=greg@kroah.com \
--cc=andreyknvl@google.com \
--cc=bp@alien8.de \
--cc=devel@etsukata.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=syzbot+42bc0d31b9a21faebdf8@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=viro@zeniv.linux.org.uk \
--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 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).