From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Subject: Re: net/bluetooth: workqueue destruction WARNING in hci_unregister_dev To: Tejun Heo , Dmitry Vyukov References: <56C5CE85.6090808@suse.cz> <20160218174427.GG13177@mtj.duckdns.org> Cc: Marcel Holtmann , Gustavo Padovan , Johan Hedberg , "David S. Miller" , linux-bluetooth@vger.kernel.org, netdev , LKML , syzkaller , Kostya Serebryany , Alexander Potapenko , Sasha Levin , Eric Dumazet , Takashi Iwai From: Jiri Slaby Message-ID: <56C6EC62.8080107@suse.cz> Date: Fri, 19 Feb 2016 11:20:18 +0100 MIME-Version: 1.0 In-Reply-To: <20160218174427.GG13177@mtj.duckdns.org> Content-Type: text/plain; charset=windows-1252 List-ID: 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 WQ_MEM_RECLAIM makes the issue go away, see whether the attached > patch works too. Hello, 1. didn't help, the problem persists. So I haven't applied the patch from 2. thanks, -- js suse labs From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jiri Slaby Subject: Re: net/bluetooth: workqueue destruction WARNING in hci_unregister_dev Date: Fri, 19 Feb 2016 11:20:18 +0100 Message-ID: <56C6EC62.8080107@suse.cz> References: <56C5CE85.6090808@suse.cz> <20160218174427.GG13177@mtj.duckdns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Cc: Marcel Holtmann , Gustavo Padovan , Johan Hedberg , "David S. Miller" , linux-bluetooth-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, netdev , LKML , syzkaller , Kostya Serebryany , Alexander Potapenko , Sasha Levin , Eric Dumazet , Takashi Iwai To: Tejun Heo , Dmitry Vyukov Return-path: In-Reply-To: <20160218174427.GG13177-qYNAdHglDFBN0TnZuCh8vA@public.gmane.org> Sender: linux-bluetooth-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: netdev.vger.kernel.org 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 WQ_MEM_RECLAIM makes the issue go away, see whether the attached > patch works too. Hello, 1. didn't help, the problem persists. So I haven't applied the patch from 2. thanks, -- js suse labs