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: Tue, 22 Mar 2016 09:09:50 +0100 Message-ID: <56F0FDCE.1040701@suse.cz> References: <56C5CE85.6090808@suse.cz> <20160218174427.GG13177@mtj.duckdns.org> <56C6EC62.8080107@suse.cz> <56C70618.3010902@suse.cz> <20160302154507.GC4282@mtj.duckdns.org> <56D7FFE1.90900@suse.cz> <20160311171205.GB24046@htj.duckdns.org> <56EA9C4D.2080803@suse.cz> <20160318205231.GO20028@mtj.duckdns.org> <56F01A1C.40208@suse.cz> 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: <56F01A1C.40208-AlSwsSmVLrQ@public.gmane.org> Sender: linux-bluetooth-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: netdev.vger.kernel.org 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=ffff88002f590300 >>>>> wq->dfl_pwq=ffff88002f591e00 pwq->refcnt=2 pwq->nr_active=0 delayed_works: >>>>> pwq 12: cpus=0-1 node=0 flags=0x4 nice=-20 active=0/1 >>>>> in-flight: 18568:wq_barrier_func >>>> >>>> So, this means that there's flush_work() racing against workqueue >>>> destruction, which can't be safe. :( >>> >>> But I cannot trigger the WARN_ONs in the attached patch, so I am >>> confused how this can happen :(. (While I am still seeing the destroy >>> WARNINGs.) >> >> So, no operations should be in progress when destroy_workqueue() is >> called. If somebody was flushing a work item, the flush call must >> have returned before destroy_workqueue() was invoked, which doesn't >> seem to be the case here. Can you trigger BUG_ON() or sysrq-t when >> the above triggers? There must be a task which is flushing a work >> item there and it shouldn't be difficult to pinpoint what's going on >> from it. > > The output of sysrq-t is here (> 200k), but I cannot see anything > suspicious in it: > http://www.fi.muni.cz/~xslaby/sklad/panics/jctl.txt Hmm, so I seem I cannot reproduce with this hunk: --- a/net/bluetooth/hci_core.c +++ b/net/bluetooth/hci_core.c @@ -3139,10 +3139,10 @@ void hci_unregister_dev(struct hci_dev *hdev) list_del(&hdev->list); write_unlock(&hci_dev_list_lock); - hci_dev_do_close(hdev); - cancel_work_sync(&hdev->power_on); + hci_dev_do_close(hdev); + if (!test_bit(HCI_INIT, &hdev->flags) && !hci_dev_test_flag(hdev, HCI_SETUP) && !hci_dev_test_flag(hdev, HCI_CONFIG)) { I cannot explain why though. I do not see how it matters in this particular case... Dmitry, could you apply it too? But I don't know how often you see the warning. PS. next on the table is the gsm tty warning. thanks, -- js suse labs