Re: [syzbot] upstream test error: WARNING in __queue_work

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: [syzbot] upstream test error: WARNING in __queue_work
From: Luiz Augusto von Dentz <luiz.dentz@xxxxxxxxx>
Date: Tue, 30 Aug 2022 10:37:07 -0700
Cc: syzbot <syzbot+243b7d89777f90f7613b@xxxxxxxxxxxxxxxxxxxxxxxxx>, LKML <linux-kernel@xxxxxxxxxxxxxxx>, syzkaller-bugs@xxxxxxxxxxxxxxxx, Tejun Heo <tj@xxxxxxxxxx>, Marcel Holtmann <marcel@xxxxxxxxxxxx>, Johan Hedberg <johan.hedberg@xxxxxxxxx>, "linux-bluetooth@xxxxxxxxxxxxxxx" <linux-bluetooth@xxxxxxxxxxxxxxx>
In-reply-to: <CAJhGHyDPN0CWZD8PxFHoB66f6QBNFGx8Lwz9EG-kSB8Q2yriQw@mail.gmail.com>
References: <00000000000016512d05e76bd837@google.com> <CAJhGHyDPN0CWZD8PxFHoB66f6QBNFGx8Lwz9EG-kSB8Q2yriQw@mail.gmail.com>

Hi Lai,

On Tue, Aug 30, 2022 at 7:08 AM Lai Jiangshan <jiangshanlai@xxxxxxxxx> wrote:
>
> CC: BLUETOOTH SUBSYSTEM
>
> It seems that hci_cmd_timeout() queues a work to a destroyed workqueue.

Are there any traces or a way to reproduce the problem?

-- 
Luiz Augusto von Dentz

Follow-Ups:
- Re: [syzbot] upstream test error: WARNING in __queue_work
  - From: Aleksandr Nogikh

References:
- Re: [syzbot] upstream test error: WARNING in __queue_work
  - From: Lai Jiangshan

Prev by Date: Re: [PATCH] adapter: Implement PowerState property
Next by Date: Re: possible deadlock in rfcomm_sk_state_change
Previous by thread: Re: [syzbot] upstream test error: WARNING in __queue_work
Next by thread: Re: [syzbot] upstream test error: WARNING in __queue_work
Index(es):
- Date
- Thread

[Index of Archives] [Bluez Devel] [Linux Wireless Networking] [Linux Wireless Personal Area Networking] [Linux ATH6KL] [Linux USB Devel] [Linux Media Drivers] [Linux Audio Users] [Linux Kernel] [Linux SCSI] [Big List of Linux Books]

Powered by Linux