Received: by 2002:a05:6a10:9afc:0:0:0:0 with SMTP id t28csp3688937pxm; Tue, 1 Mar 2022 03:33:34 -0800 (PST) X-Google-Smtp-Source: ABdhPJwOz3RrBHLfcl73zwYQcx+qse5LrO5RVUTLZ8PxYvsuPjLdV374kPdkSJhAJnjBM4lQTR4J X-Received: by 2002:a17:906:a92:b0:6ce:6f8b:a1ba with SMTP id y18-20020a1709060a9200b006ce6f8ba1bamr18835992ejf.715.1646134413893; Tue, 01 Mar 2022 03:33:33 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1646134413; cv=none; d=google.com; s=arc-20160816; b=iHesZnSINk84ZF3fWyLSe4kKY6fABxZk7SOafYzaLDwAU6BJ0NxCQHdMJgKEbsBEFt e0Xt7NZ/rlZvbE6bPLglkL7ZxsNzfulPuWM75otQedLo3pWSTW/f/YQi87GmtOFxnl9E BFJlBUJ/SpuQnmF+1llP173+QSHC4k9Po0N/KghPK7bFW4Rbde6Ehc3VEFD5um4Rbm7Q 8Z6fhVYAlON+ovsBEcaU9nmNNRluWNE4ICeaF9ifQDIaW9piiifeD86l94dPjEt79pO6 d/vULvA/U9xW2zWXIq0zBUHvLtrXdtz1gvJ8utrHnPnuV5Tk5mpmtk/kMTgzgiGuvjLr dO1A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=MyK8CGeqc8W1ttSv05bq0b6rSbbQ2JkU82/9ujV/uPI=; b=mhP/55kvkX9fTPk9F2ZAIWx0wEEV+X+53Bl/7TrIk+i+1ce0pKJ+HcPE1IJikKcbL5 gPFcQBIuONAh5Cc6sZ8M1zqqDrrjFaRzWvNRA2UNfwizBkyMA603HtRxOvENGU5sNayI zoPe++NkKyS1i9M4Xv4oeZLpsNGCoUCsZWgEJ5TaudXAFBd4N6lRYVEfsvGRf/fj2AS+ R5DXUB9utQdT1ENJLQSf667rJ23HIOEbiAFYnTidKlCIslqCU5JzQySzaUPCiUFy2H87 te1MYvey1RwPab0g3cHkoU27OoQ89Uc/kNSd9FexrOJJKt3Yz/QZKu5gzWzDrlYSsThH sBnQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=jORoIMPJ; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id r15-20020aa7da0f000000b00412cd348935si8488607eds.426.2022.03.01.03.33.10; Tue, 01 Mar 2022 03:33:33 -0800 (PST) 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; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=jORoIMPJ; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234010AbiCAKaI (ORCPT + 99 others); Tue, 1 Mar 2022 05:30:08 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:55980 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233602AbiCAKaF (ORCPT ); Tue, 1 Mar 2022 05:30:05 -0500 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id ACC858E19F for ; Tue, 1 Mar 2022 02:29:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1646130556; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=MyK8CGeqc8W1ttSv05bq0b6rSbbQ2JkU82/9ujV/uPI=; b=jORoIMPJ2MC0KT+04w0PMGCB6tc6bPPatRJx0ToEJl+be2vE+E/38UMDW8RDl6AzoGWo/7 twPGjOENWQhzYUKPWbffN9eMAF/xWwU/nu6XR5l99xg/e/KLwbmvVNzTOmeXbYpsiIH1Zc b02C7EGDKNXucLTp14RFgFXcYQ3yXFY= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-353-vtR9JpqPPUqdZT2yhI3tpw-1; Tue, 01 Mar 2022 05:29:13 -0500 X-MC-Unique: vtR9JpqPPUqdZT2yhI3tpw-1 Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.phx2.redhat.com [10.5.11.13]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id D4D4CFC80; Tue, 1 Mar 2022 10:29:11 +0000 (UTC) Received: from T590 (ovpn-8-17.pek2.redhat.com [10.72.8.17]) by smtp.corp.redhat.com (Postfix) with ESMTPS id EE0596F965; Tue, 1 Mar 2022 10:29:06 +0000 (UTC) Date: Tue, 1 Mar 2022 18:29:01 +0800 From: Ming Lei To: Christoph Hellwig Cc: Yu Kuai , tj@kernel.org, axboe@kernel.dk, cgroups@vger.kernel.org, linux-block@vger.kernel.org, linux-kernel@vger.kernel.org, yi.zhang@huawei.com Subject: Re: [PATCH v9] block: cancel all throttled bios in del_gendisk() Message-ID: References: <20220210115637.1074927-1-yukuai3@huawei.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Scanned-By: MIMEDefang 2.79 on 10.5.11.13 X-Spam-Status: No, score=-3.2 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H5,RCVD_IN_MSPIKE_WL,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 Mon, Feb 28, 2022 at 01:40:53AM -0800, Christoph Hellwig wrote: > On Mon, Feb 28, 2022 at 02:11:30PM +0800, Ming Lei wrote: > > > FYI, this crashed left rigt and center when running xfstests with > > > traces pointing to throtl_pending_timer_fn. > > > > Can you share the exact xfstests test(fs, test)? Or panic log? > > > > I can't reproduce it when running './check -g auto' on XFS, meantime > > tracking throtl_pending_timer_fn(). > > From a quick run using f2fs: > > generic/081 files ... [ 316.487861] run fstests generic/081 at 2022-02-28 09:38:40 Thanks for providing the reproducer. The reason is that the pending timer is deleted in blkg's release handler, so the timer can still be live after request queue is released. The patch of 'block: cancel all throttled bios in del_gendisk()' should just make it easier to trigger. After patch of "block: move blkcg initialization/destroy into disk allocation/ release handler" lands, the issue can be fixed easily by: diff --git a/block/blk-cgroup.c b/block/blk-cgroup.c index fa063c6c0338..e8d4be5e1de3 100644 --- a/block/blk-cgroup.c +++ b/block/blk-cgroup.c @@ -82,6 +82,7 @@ static void blkg_free(struct blkcg_gq *blkg) if (blkg->pd[i]) blkcg_policy[i]->pd_free_fn(blkg->pd[i]); + blk_put_queue(blkg->q); free_percpu(blkg->iostat_cpu); percpu_ref_exit(&blkg->refcnt); kfree(blkg); @@ -297,9 +298,10 @@ static struct blkcg_gq *blkg_create(struct blkcg *blkcg, blkg->online = true; spin_unlock(&blkcg->lock); - if (!ret) + if (!ret && blk_get_queue(q)) return blkg; - + else if (!ret) + ret = -ENODEV; /* @blkg failed fully initialized, use the usual release path */ blkg_put(blkg); return ERR_PTR(ret); Thanks, Ming