From: patchwork-bot+bluetooth@kernel.org
To: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Cc: marcel@holtmann.org, johan.hedberg@gmail.com,
luiz.dentz@gmail.com, schspa@gmail.com,
syzbot+243b7d89777f90f7613b@syzkaller.appspotmail.com,
syzkaller-bugs@googlegroups.com, jiangshanlai@gmail.com,
tj@kernel.org, linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: use hdev->workqueue when queuing hdev->{cmd,ncmd}_timer works
Date: Mon, 19 Sep 2022 17:30:16 +0000 [thread overview]
Message-ID: <166360861658.29822.12630760382749336060.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <733e6931-aa66-5295-d8a8-49063b7347f1@I-love.SAKURA.ne.jp>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Fri, 2 Sep 2022 20:23:48 +0900 you wrote:
> syzbot is reporting attempt to schedule hdev->cmd_work work from system_wq
> WQ into hdev->workqueue WQ which is under draining operation [1], for
> commit c8efcc2589464ac7 ("workqueue: allow chained queueing during
> destruction") does not allow such operation.
>
> The check introduced by commit 877afadad2dce8aa ("Bluetooth: When HCI work
> queue is drained, only queue chained work") was incomplete.
>
> [...]
Here is the summary with links:
- Bluetooth: use hdev->workqueue when queuing hdev->{cmd,ncmd}_timer works
https://git.kernel.org/bluetooth/bluetooth-next/c/deee93d13d38
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-09-19 17:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <00000000000016512d05e76bd837@google.com>
2022-08-30 14:08 ` [syzbot] upstream test error: WARNING in __queue_work Lai Jiangshan
2022-08-30 17:37 ` Luiz Augusto von Dentz
2022-09-02 12:28 ` Aleksandr Nogikh
2022-09-02 11:23 ` [PATCH] Bluetooth: use hdev->workqueue when queuing hdev->{cmd,ncmd}_timer works Tetsuo Handa
2022-09-02 12:00 ` bluez.test.bot
2022-09-02 18:45 ` [PATCH] " Luiz Augusto von Dentz
2022-09-02 21:31 ` Luiz Augusto von Dentz
2022-09-03 6:49 ` Tetsuo Handa
2022-09-04 2:11 ` Luiz Augusto von Dentz
2022-09-04 2:20 ` Tejun Heo
2022-09-05 8:24 ` Schspa Shi
2022-09-05 11:23 ` Tetsuo Handa
2022-09-05 12:26 ` Schspa Shi
2022-09-19 17:30 ` 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=166360861658.29822.12630760382749336060.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=jiangshanlai@gmail.com \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=schspa@gmail.com \
--cc=syzbot+243b7d89777f90f7613b@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tj@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox