mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Akhil Arul <akhilarul324@gmail.com>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com,
	linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
	syzkaller-bugs@googlegroups.com,
	syzbot+2344fb8002f3ef5b1712@syzkaller.appspotmail.com
Subject: Re: [PATCH] Bluetooth: hci_core: Fix queuing rx_work while workqueue is drained
Date: Fri, 23 Oct 2026 21:00:39 +0000	[thread overview]
Message-ID: <179278923956.1268720.15284721723706023982.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261023161609.253097-1-akhilarul324@gmail.com>

Hello:

This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:

On Fri, 23 Oct 2026 21:46:09 +0530 you wrote:
> hci_recv_frame() drops a frame unless HCI_UP or HCI_INIT is set, but the
> check is not synchronized with hci_dev_close_sync().  A driver can pass
> the check, then close clears HCI_UP, flushes rx_work and starts
> drain_workqueue(), and the late queue_work() of rx_work hits the
> draining workqueue:
> 
>   workqueue: cannot queue hci_rx_work on wq hci0
>   WARNING: kernel/workqueue.c:2352 at __queue_work+0x2c0/0x780
>   Call Trace:
>    queue_work_on+0xb2/0xc0
>    hci_recv_frame+0x18f/0x330
>    vhci_write+0x174/0x240
>    vfs_write+0x271/0x680
>    ksys_write+0x7c/0x110
> 
> [...]

Here is the summary with links:
  - Bluetooth: hci_core: Fix queuing rx_work while workqueue is drained
    https://git.kernel.org/bluetooth/bluetooth-next/c/63bcf9f4a40d

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      reply	other threads:[~2026-10-23 21:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-23 16:16 Akhil Arul
2026-10-23 21:00 ` patchwork-bot+bluetooth [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=179278923956.1268720.15284721723706023982.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=akhilarul324@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.org \
    --cc=syzbot+2344fb8002f3ef5b1712@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
all inboxes | Powered by JetHome®