From: syzbot <syzbot+e7be5be00de0c3c2d782@syzkaller.appspotmail.com>
To: atul.droid@gmail.com, davem@davemloft.net, edumazet@google.com,
johan.hedberg@gmail.com, kuba@kernel.org,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
luiz.dentz@gmail.com, luiz.von.dentz@intel.com,
marcel@holtmann.org, netdev@vger.kernel.org, pabeni@redhat.com,
rauji.raut@gmail.com, syzkaller-bugs@googlegroups.com,
yinghsu@chromium.org
Subject: Re: [syzbot] [bluetooth?] BUG: sleeping function called from invalid context in hci_cmd_sync_submit
Date: Fri, 15 Dec 2023 14:47:05 -0800 [thread overview]
Message-ID: <000000000000e9c652060c942d35@google.com> (raw)
In-Reply-To: <00000000000011da7605ffa4d289@google.com>
syzbot suspects this issue was fixed by commit:
commit c7eaf80bfb0c8cef852cce9501b95dd5a6bddcb9
Author: Ying Hsu <yinghsu@chromium.org>
Date: Mon Sep 4 14:11:51 2023 +0000
Bluetooth: Fix hci_link_tx_to RCU lock usage
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=16dbe571e80000
start commit: 9fdfb15a3dbf Merge tag 'net-6.6-rc2' of git://git.kernel.o..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=df91a3034fe3f122
dashboard link: https://syzkaller.appspot.com/bug?extid=e7be5be00de0c3c2d782
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=165c9c64680000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15f91628680000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: Bluetooth: Fix hci_link_tx_to RCU lock usage
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2023-12-15 22:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-04 8:10 [syzbot] [bluetooth?] BUG: sleeping function called from invalid context in hci_cmd_sync_submit syzbot
2023-09-17 4:59 ` syzbot
2023-12-15 22: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=000000000000e9c652060c942d35@google.com \
--to=syzbot+e7be5be00de0c3c2d782@syzkaller.appspotmail.com \
--cc=atul.droid@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=johan.hedberg@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=luiz.von.dentz@intel.com \
--cc=marcel@holtmann.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rauji.raut@gmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=yinghsu@chromium.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.