From: syzbot <syzbot+f2725165900304ec97b6@syzkaller.appspotmail.com>
To: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
Cc: fmdefrancesco@gmail.com, johan.hedberg@gmail.com,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
luiz.dentz@gmail.com, marcel@holtmann.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] INFO: trying to register non-static key in hci_uart_tty_receive (3)
Date: Sat, 23 Oct 2021 06:47:12 -0700 [thread overview]
Message-ID: <0000000000006baa3205cf055dd1@google.com> (raw)
In-Reply-To: <4202176.J8ZBFPDcmx@localhost.localdomain>
> On Saturday, October 23, 2021 1:54:24 AM CEST syzbot wrote:
>> Hello,
>>
>> syzbot found the following issue on:
>>
>> HEAD commit: 519d81956ee2 Linux 5.15-rc6
>> git tree: upstream
>> console output: https://syzkaller.appspot.com/x/log.txt?x=16787178b00000
>> kernel config: https://syzkaller.appspot.com/x/.config?x=1f7f46d98a0da80e
>> dashboard link: https://syzkaller.appspot.com/bug?
> extid=f2725165900304ec97b6
>> compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils
> for Debian) 2.35.2
>>
>> Unfortunately, I don't have any reproducer for this issue yet.
>>
>> IMPORTANT: if you fix the issue, please add the following tag to the
> commit:
>> Reported-by: syzbot+f2725165900304ec97b6@syzkaller.appspotmail.com
>>
>> INFO: trying to register non-static key.
>> The code is fine but needs lockdep annotation, or maybe
>> you didn't initialize this object before use?
>> turning off the locking correctness validator.
>
> Let's try the solution attached.
>
> Fabio
>
> #syz test
This crash does not have a reproducer. I cannot test it.
> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
prev parent reply other threads:[~2021-10-23 13:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-22 23:54 [syzbot] INFO: trying to register non-static key in hci_uart_tty_receive (3) syzbot
2021-10-23 13:47 ` Fabio M. De Francesco
2021-10-23 13:47 ` 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=0000000000006baa3205cf055dd1@google.com \
--to=syzbot+f2725165900304ec97b6@syzkaller.appspotmail.com \
--cc=fmdefrancesco@gmail.com \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=syzkaller-bugs@googlegroups.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