From: syzbot <syzbot+7d51f807c81b190a127d@syzkaller.appspotmail.com>
To: davem@davemloft.net, desmondcheongzx@gmail.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,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] INFO: task can't die in __lock_sock
Date: Wed, 01 Sep 2021 18:34:11 -0700 [thread overview]
Message-ID: <0000000000000840d605caf92e8e@google.com> (raw)
In-Reply-To: <000000000000b1c39505c99bd67c@google.com>
syzbot has bisected this issue to:
commit b7ce436a5d798bc59e71797952566608a4b4626b
Author: Desmond Cheong Zhi Xi <desmondcheongzx@gmail.com>
Date: Tue Aug 10 04:14:09 2021 +0000
Bluetooth: switch to lock_sock in RFCOMM
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=16f90ffe300000
start commit: 29ce8f970107 Merge git://git.kernel.org/pub/scm/linux/kern..
git tree: net-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=15f90ffe300000
console output: https://syzkaller.appspot.com/x/log.txt?x=11f90ffe300000
kernel config: https://syzkaller.appspot.com/x/.config?x=d2f9d4c9ff8c5ae7
dashboard link: https://syzkaller.appspot.com/bug?extid=7d51f807c81b190a127d
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1630a66d300000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16d07c6d300000
Reported-by: syzbot+7d51f807c81b190a127d@syzkaller.appspotmail.com
Fixes: b7ce436a5d79 ("Bluetooth: switch to lock_sock in RFCOMM")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2021-09-02 1:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-15 16:47 [syzbot] INFO: task can't die in __lock_sock syzbot
2021-09-01 17:34 ` syzbot
2021-09-02 1:34 ` syzbot [this message]
[not found] ` <20210902031752.2502-1-hdanton@sina.com>
2021-09-02 19:54 ` Desmond Cheong Zhi Xi
[not found] <20210920142348.4642-1-hdanton@sina.com>
2021-09-20 15:50 ` syzbot
2021-09-22 14:16 ` Thomas Gleixner
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=0000000000000840d605caf92e8e@google.com \
--to=syzbot+7d51f807c81b190a127d@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=desmondcheongzx@gmail.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=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 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.