public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Hillf Danton <hdanton@sina.com>
To: syzbot <syzbot+91dbdfecdd3287734d8e@syzkaller.appspotmail.com>
Cc: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bluetooth?] possible deadlock in touch_wq_lockdep_map
Date: Wed,  3 Jul 2024 18:26:33 +0800	[thread overview]
Message-ID: <20240703102633.2821-1-hdanton@sina.com> (raw)
In-Reply-To: <000000000000fb901b061c4e0282@google.com>

On Tue, 02 Jul 2024 18:47:23 -0700
> syzbot has found a reproducer for the following issue on:
> 
> HEAD commit:    734610514cb0 Merge tag 'erofs-for-6.10-rc7-fixes' of git:/..
> git tree:       upstream
> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=1424d281980000

#syz test https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git  734610514cb0

--- x/net/bluetooth/hci_core.c
+++ y/net/bluetooth/hci_core.c
@@ -1075,6 +1075,7 @@ static void hci_power_off(struct work_st
 static void hci_error_reset(struct work_struct *work)
 {
 	struct hci_dev *hdev = container_of(work, struct hci_dev, error_reset);
+	bool put;
 
 	hci_dev_hold(hdev);
 	BT_DBG("%s", hdev->name);
@@ -1084,10 +1085,13 @@ static void hci_error_reset(struct work_
 	else
 		bt_dev_err(hdev, "hardware error 0x%2.2x", hdev->hw_error_code);
 
+	put = !test_bit(HCI_UP, &hdev->flags);
+
 	if (!hci_dev_do_close(hdev))
 		hci_dev_do_open(hdev);
 
-	hci_dev_put(hdev);
+	if (put)
+		hci_dev_put(hdev);
 }
 
 void hci_uuids_clear(struct hci_dev *hdev)
--

  reply	other threads:[~2024-07-03 10:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-16 14:29 [syzbot] [bluetooth?] possible deadlock in touch_wq_lockdep_map syzbot
2024-07-03  1:47 ` syzbot
2024-07-03 10:26   ` Hillf Danton [this message]
2024-07-03 10:54     ` syzbot
2024-07-26  3:20 ` syzbot
2024-07-26  9:00   ` Eli Billauer

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=20240703102633.2821-1-hdanton@sina.com \
    --to=hdanton@sina.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzbot+91dbdfecdd3287734d8e@syzkaller.appspotmail.com \
    --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