From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id A9C4FC04A68 for ; Thu, 28 Jul 2022 12:26:20 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S238453AbiG1M0T (ORCPT ); Thu, 28 Jul 2022 08:26:19 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:36250 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S238173AbiG1M0R (ORCPT ); Thu, 28 Jul 2022 08:26:17 -0400 Received: from www262.sakura.ne.jp (www262.sakura.ne.jp [202.181.97.72]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 510FE52FE4 for ; Thu, 28 Jul 2022 05:26:17 -0700 (PDT) Received: from fsav111.sakura.ne.jp (fsav111.sakura.ne.jp [27.133.134.238]) by www262.sakura.ne.jp (8.15.2/8.15.2) with ESMTP id 26SCPrv4091076; Thu, 28 Jul 2022 21:25:53 +0900 (JST) (envelope-from penguin-kernel@I-love.SAKURA.ne.jp) Received: from www262.sakura.ne.jp (202.181.97.72) by fsav111.sakura.ne.jp (F-Secure/fsigk_smtp/550/fsav111.sakura.ne.jp); Thu, 28 Jul 2022 21:25:53 +0900 (JST) X-Virus-Status: clean(F-Secure/fsigk_smtp/550/fsav111.sakura.ne.jp) Received: from [192.168.1.9] (M106072142033.v4.enabler.ne.jp [106.72.142.33]) (authenticated bits=0) by www262.sakura.ne.jp (8.15.2/8.15.2) with ESMTPSA id 26SCPr5O091072 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=NO); Thu, 28 Jul 2022 21:25:53 +0900 (JST) (envelope-from penguin-kernel@I-love.SAKURA.ne.jp) Message-ID: <49e04fb8-e8fe-17d3-0b5f-e8d255010936@I-love.SAKURA.ne.jp> Date: Thu, 28 Jul 2022 21:25:50 +0900 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 6.3; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.11.0 Subject: Re: [syzbot] INFO: task hung in hci_dev_close_sync Content-Language: en-US To: Johannes Berg , Tejun Heo Cc: "linux-kernel@vger.kernel.org" , Dmitry Vyukov , "syzkaller-bugs@googlegroups.com" , Hillf Danton , syzbot References: <20220504044800.4966-1-hdanton@sina.com> <05280c37163d08ff2d00d71c5454baf651867bd3.camel@sipsolutions.net> From: Tetsuo Handa In-Reply-To: <05280c37163d08ff2d00d71c5454baf651867bd3.camel@sipsolutions.net> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2022/05/04 18:24, Johannes Berg wrote: > On Wed, 2022-05-04 at 05:12 +0000, Tetsuo Handa wrote: >> >> This seems to be a question regarding commit 87915adc3f0acdf0 ("workqueue: re-add lockdep dependencies for flushing"). >>> >>> syzbot should have been able to catch cancel_work_sync() in work context >>> by checking lockdep_map in __flush_work() for both flush and cancel. >>> >>> Hillf >>> >>> --- y/kernel/workqueue.c >>> +++ x/kernel/workqueue.c >>> @@ -3075,10 +3075,10 @@ static bool __flush_work(struct work_str >>> if (WARN_ON(!work->func)) >>> return false; >>> >>> - if (!from_cancel) { >>> + //if (!from_cancel) { >>> > > I think this is explained in commit d6e89786bed9 ("workqueue: skip > lockdep wq dependency in cancel_work_sync()") I couldn't agree on that reasoning, and I sent https://lkml.kernel.org/r/21b9c1ac-64b7-7f4b-1e62-bf2f021fffcd@I-love.SAKURA.ne.jp .