Received: by 2002:a05:6a10:2726:0:0:0:0 with SMTP id ib38csp1374373pxb; Wed, 30 Mar 2022 01:49:55 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxK00pSRx9KNdunHJObFs7hFpeXw8BLxffl5MVCcp0Ifif7UJn8ia8X1KSQ1AdOsC3MSQsB X-Received: by 2002:a05:6402:168a:b0:3fb:600e:4cc3 with SMTP id a10-20020a056402168a00b003fb600e4cc3mr9397265edv.32.1648630195214; Wed, 30 Mar 2022 01:49:55 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1648630195; cv=none; d=google.com; s=arc-20160816; b=cAvN12RMHZPFb65I9Rfl9NLNTtJ3BmzE700woebbFI41jyaUVPEVXe+KzUiuLlC4Lu eVo313LIeQndW8O9LzxEB6r7+Ad3ZmU2ozT4uSzU8fd17NHROdxnBFru9lZCQ8FiYMbw zxhhWHsgd673Dii5DDNhlSfcM3ux2PAbu2n87/2SM7NgMKu1WhInrY3Cc996ehi7lBHr ybdACtFU/rR+KOnRBaaFX8e316m4YMBWR1GOOiM8uxHuzMGwAJxySAP6UFbnrj1nA8nC PTtZ97retSS+wGSWodzsFrnjnejfoeVxhAc+RnA6n7rmmhtfrSAViH5sqUt1FRiTaVl1 9hVw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:from :references:cc:to:content-language:subject:user-agent:mime-version :date:message-id; bh=Xeg9G/6MTts45KE446MOS9MLJgMqAZgv4wl7Sk42RFY=; b=eF6H4YXykW3kTO5kYDTSe9UOhVm2Q1geGsvglTl/YOmLajUs9h64uQIoWejEiLmyue JolZW0LEAu3uoDw4UAIG8Pyk6vQXc9uJ+3+jHXauUMtRd5FtJ1h+RtzRGhlrONIF7RhC UhP/rURSMtf/Ikf50SpAi0SoQzTo5R6vXe9awoGQSU1aUvcp2RrylFUgsC4+7LbxG+SD TWI8mnKW1RUXcx/7dNYeT7miVbsTNYNNHlI4ZdNK31iMSSneoGLEGhleOG7HRhBHWq6A y3yBYm+cMM4zCPXb0kvUk7fxo2lobs0g/tIUql6B6voqu2vn75Ms1/IR7Mnbfl+aMbe7 p5mg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id o17-20020aa7c511000000b004190f92367esi20205275edq.222.2022.03.30.01.49.27; Wed, 30 Mar 2022 01:49:54 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S242120AbiC3CvW (ORCPT + 99 others); Tue, 29 Mar 2022 22:51:22 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:59710 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S242113AbiC3CvU (ORCPT ); Tue, 29 Mar 2022 22:51:20 -0400 Received: from www262.sakura.ne.jp (www262.sakura.ne.jp [202.181.97.72]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id CBE54632C for ; Tue, 29 Mar 2022 19:49:36 -0700 (PDT) Received: from fsav113.sakura.ne.jp (fsav113.sakura.ne.jp [27.133.134.240]) by www262.sakura.ne.jp (8.15.2/8.15.2) with ESMTP id 22U2nAgB017937; Wed, 30 Mar 2022 11:49:10 +0900 (JST) (envelope-from penguin-kernel@I-love.SAKURA.ne.jp) Received: from www262.sakura.ne.jp (202.181.97.72) by fsav113.sakura.ne.jp (F-Secure/fsigk_smtp/550/fsav113.sakura.ne.jp); Wed, 30 Mar 2022 11:49:10 +0900 (JST) X-Virus-Status: clean(F-Secure/fsigk_smtp/550/fsav113.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 22U2nAA2017933 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=NO); Wed, 30 Mar 2022 11:49:10 +0900 (JST) (envelope-from penguin-kernel@I-love.SAKURA.ne.jp) Message-ID: Date: Wed, 30 Mar 2022 11:49:07 +0900 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 6.3; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.7.0 Subject: Re: [syzbot] possible deadlock in p9_write_work Content-Language: en-US To: Dominique Martinet Cc: Andrew Perepechko , Andreas Dilger , "Theodore Ts'o" , syzbot , linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com, v9fs-developer@lists.sourceforge.net, "open list:EXT4 FILE SYSTEM" References: <0000000000009523b605db620972@google.com> <385ce718-f965-4005-56b6-34922c4533b8@I-love.SAKURA.ne.jp> From: Tetsuo Handa In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,NICE_REPLY_A, SPF_HELO_NONE,SPF_NONE,T_SCC_BODY_TEXT_LINE autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2022/03/30 11:29, Dominique Martinet wrote: > Tetsuo Handa wrote on Wed, Mar 30, 2022 at 10:57:15AM +0900: >>>> Please don't use schedule_work() if you need to use flush_scheduled_work(). >>> >>> In this case we don't call flush_scheduled_work -- ext4 does. >> >> Yes, that's why I changed recipients to ext4 people. > > Sorry, I hadn't noticed. > 9p is the one calling schedule_work, so ultimately it really is the > combinaison of the two, and not just ext4 that's wrong here. Calling schedule_work() itself does not cause troubles (unless there are too many pending works to make progress). Calling flush_scheduled_work() causes troubles because it waits for completion of all works even if some of works cannot be completed due to locks held by the caller of flush_scheduled_work(). 9p is innocent for this report.