Re: net/bluetooth: workqueue destruction WARNING in hci_unregister_dev

Hello, On Tue, Sep 13, 2016 at 08:14:40PM +0200, Jiri Slaby wrote: > I assume Dmitry sees the same what I am still seeing, so I reported this > some time ago: > https://lkml.org/lkml/2016/3/21/492 > > This warning is trigerred there and still occurs with "HEAD": > (pwq != wq->dfl_pwq) &&

Re: net/bluetooth: workqueue destruction WARNING in hci_unregister_dev

On 09/13/2016, 05:35 PM, Tejun Heo wrote: > Hello, > > On Sat, Sep 10, 2016 at 11:33:48AM +0200, Dmitry Vyukov wrote: >> Hit the WARNING with the patch. It showed "Showing busy workqueues and >> worker pools:" after the WARNING, but then no queue info. Was it >> already destroyed and removed from

Re: net/bluetooth: workqueue destruction WARNING in hci_unregister_dev

Hello, On Sat, Sep 10, 2016 at 11:33:48AM +0200, Dmitry Vyukov wrote: > Hit the WARNING with the patch. It showed "Showing busy workqueues and > worker pools:" after the WARNING, but then no queue info. Was it > already destroyed and removed from the list?... Hmm... It either means that the

Re: net/bluetooth: workqueue destruction WARNING in hci_unregister_dev

On Mon, Sep 5, 2016 at 3:14 PM, Dmitry Vyukov wrote: > On Mon, Sep 5, 2016 at 3:08 PM, Tejun Heo wrote: >> Hello, >> >> On Sat, Sep 03, 2016 at 12:58:33PM +0200, Dmitry Vyukov wrote: >>> > I've seen it only several times in several months, so I don't it will

Re: net/bluetooth: workqueue destruction WARNING in hci_unregister_dev

On Mon, Sep 5, 2016 at 3:08 PM, Tejun Heo wrote: > Hello, > > On Sat, Sep 03, 2016 at 12:58:33PM +0200, Dmitry Vyukov wrote: >> > I've seen it only several times in several months, so I don't it will >> > be helpful. >> >> >> Bad news: I hit it again. >> On

Re: net/bluetooth: workqueue destruction WARNING in hci_unregister_dev

Hello, On Sat, Sep 03, 2016 at 12:58:33PM +0200, Dmitry Vyukov wrote: > > I've seen it only several times in several months, so I don't it will > > be helpful. > > > Bad news: I hit it again. > On 0f98f121e1670eaa2a2fbb675e07d6ba7f0e146f of linux-next, so I have >

Re: net/bluetooth: workqueue destruction WARNING in hci_unregister_dev

On Tue, Mar 22, 2016 at 1:32 PM, Dmitry Vyukov wrote: > On Tue, Mar 22, 2016 at 9:09 AM, Jiri Slaby wrote: >> On 03/21/2016, 04:58 PM, Jiri Slaby wrote: >>> Hello, >>> >>> On 03/18/2016, 09:52 PM, Tejun Heo wrote: On Thu, Mar 17, 2016 at 01:00:13PM +0100,

Re: net/bluetooth: workqueue destruction WARNING in hci_unregister_dev

On Tue, Mar 22, 2016 at 9:09 AM, Jiri Slaby wrote: > On 03/21/2016, 04:58 PM, Jiri Slaby wrote: >> Hello, >> >> On 03/18/2016, 09:52 PM, Tejun Heo wrote: >>> On Thu, Mar 17, 2016 at 01:00:13PM +0100, Jiri Slaby wrote: >> I have not done that yet, but today, I see: >>

Re: net/bluetooth: workqueue destruction WARNING in hci_unregister_dev

On 03/21/2016, 04:58 PM, Jiri Slaby wrote: > Hello, > > On 03/18/2016, 09:52 PM, Tejun Heo wrote: >> On Thu, Mar 17, 2016 at 01:00:13PM +0100, Jiri Slaby wrote: > I have not done that yet, but today, I see: > destroy_workqueue: name='req_hci0' pwq=88002f590300 >

Re: net/bluetooth: workqueue destruction WARNING in hci_unregister_dev

Hello, On 03/18/2016, 09:52 PM, Tejun Heo wrote: > On Thu, Mar 17, 2016 at 01:00:13PM +0100, Jiri Slaby wrote: I have not done that yet, but today, I see: destroy_workqueue: name='req_hci0' pwq=88002f590300 wq->dfl_pwq=88002f591e00 pwq->refcnt=2 pwq->nr_active=0

Re: net/bluetooth: workqueue destruction WARNING in hci_unregister_dev

Hello, Jiri. On Thu, Mar 17, 2016 at 01:00:13PM +0100, Jiri Slaby wrote: > >> I have not done that yet, but today, I see: > >> destroy_workqueue: name='req_hci0' pwq=88002f590300 > >> wq->dfl_pwq=88002f591e00 pwq->refcnt=2 pwq->nr_active=0 delayed_works: > >>pwq 12: cpus=0-1 node=0

Re: net/bluetooth: workqueue destruction WARNING in hci_unregister_dev

Hello, On 03/11/2016, 06:12 PM, Tejun Heo wrote: > On Thu, Mar 03, 2016 at 10:12:01AM +0100, Jiri Slaby wrote: >> On 03/02/2016, 04:45 PM, Tejun Heo wrote: >>> On Fri, Feb 19, 2016 at 01:10:00PM +0100, Jiri Slaby wrote: > 1. didn't help, the problem persists. So I haven't applied the patch

Re: net/bluetooth: workqueue destruction WARNING in hci_unregister_dev

Hello, Sorry about the delay. On Thu, Mar 03, 2016 at 10:12:01AM +0100, Jiri Slaby wrote: > On 03/02/2016, 04:45 PM, Tejun Heo wrote: > > On Fri, Feb 19, 2016 at 01:10:00PM +0100, Jiri Slaby wrote: > >>> 1. didn't help, the problem persists. So I haven't applied the patch from > >>> 2. > >> >

Re: net/bluetooth: workqueue destruction WARNING in hci_unregister_dev

Hi, On 03/02/2016, 04:45 PM, Tejun Heo wrote: > On Fri, Feb 19, 2016 at 01:10:00PM +0100, Jiri Slaby wrote: >>> 1. didn't help, the problem persists. So I haven't applied the patch from 2. >> >> FWIW I dumped more info about the wq: >> wq->name='hci0' pwq=8800390d7600

Re: net/bluetooth: workqueue destruction WARNING in hci_unregister_dev

Hello, Jiri. On Fri, Feb 19, 2016 at 01:10:00PM +0100, Jiri Slaby wrote: > > 1. didn't help, the problem persists. So I haven't applied the patch from 2. > > FWIW I dumped more info about the wq: > wq->name='hci0' pwq=8800390d7600 wq->dfl_pwq=8800390d5200 > pwq->refcnt=2 pwq->nr_active=0

Re: net/bluetooth: workqueue destruction WARNING in hci_unregister_dev

On 02/19/2016, 11:20 AM, Jiri Slaby wrote: > On 02/18/2016, 06:44 PM, Tejun Heo wrote: >> Hello, >> >> Can you please do the followings? >> >> 1. Remove WQ_MEM_RECLAIM from the affected workqueue and see whether >>the problem is reproducible. WQ_MEM_RECLAIM on anything bluetooth >>doesn't

Re: net/bluetooth: workqueue destruction WARNING in hci_unregister_dev

On 02/18/2016, 06:44 PM, Tejun Heo wrote: > Hello, > > Can you please do the followings? > > 1. Remove WQ_MEM_RECLAIM from the affected workqueue and see whether >the problem is reproducible. WQ_MEM_RECLAIM on anything bluetooth >doesn't make sense btw. Why is it there? > > 2. If

Re: net/bluetooth: workqueue destruction WARNING in hci_unregister_dev

Hello, Can you please do the followings? 1. Remove WQ_MEM_RECLAIM from the affected workqueue and see whether the problem is reproducible. WQ_MEM_RECLAIM on anything bluetooth doesn't make sense btw. Why is it there? 2. If WQ_MEM_RECLAIM makes the issue go away, see whether the attached

Re: net/bluetooth: workqueue destruction WARNING in hci_unregister_dev

On Thu, Feb 18, 2016 at 3:00 PM, Jiri Slaby wrote: > Cc Tejun (workqueues), Takashi (debug patch) > > On 01/26/2016, 12:53 PM, Dmitry Vyukov wrote: >> Hello, >> >> I've hit the following warning while running syzkaller fuzzer: > > Hi, > > I am hitting it over and over again using

Re: net/bluetooth: workqueue destruction WARNING in hci_unregister_dev

Cc Tejun (workqueues), Takashi (debug patch) On 01/26/2016, 12:53 PM, Dmitry Vyukov wrote: > Hello, > > I've hit the following warning while running syzkaller fuzzer: Hi, I am hitting it over and over again using syzkaller. > WARNING: CPU: 2 PID: 17409 at kernel/workqueue.c:3968 >

Re: net/bluetooth: workqueue destruction WARNING in hci_unregister_dev

On Tue, Jan 26, 2016 at 12:53 PM, Dmitry Vyukov wrote: > Hello, > > I've hit the following warning while running syzkaller fuzzer: > > [ cut here ] > WARNING: CPU: 2 PID: 17409 at kernel/workqueue.c:3968 > destroy_workqueue+0x172/0x550() > Modules

net/bluetooth: workqueue destruction WARNING in hci_unregister_dev

Hello, I've hit the following warning while running syzkaller fuzzer: [ cut here ] WARNING: CPU: 2 PID: 17409 at kernel/workqueue.c:3968 destroy_workqueue+0x172/0x550() Modules linked in: CPU: 2 PID: 17409 Comm: syz-executor Not tainted 4.5.0-rc1+ #283 Hardware name: QEMU