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 DD147C433EF for ; Fri, 18 Mar 2022 07:04:26 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232895AbiCRHFm (ORCPT ); Fri, 18 Mar 2022 03:05:42 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49636 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232878AbiCRHFj (ORCPT ); Fri, 18 Mar 2022 03:05:39 -0400 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id D1C08DEAD for ; Fri, 18 Mar 2022 00:04:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1647587059; 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: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=dRxKY2ALGuJ0XownOAjggWtKbSTTBHbjSbBWPLWoaKg=; b=A7bsFf8izkMxu/V45gHtDxv47MfjIMKoBpizja7G43wNQyAjsOXceHI8T93oBoCq9YxAEu qQHko++Qw8MaW8a2pFAQEeWyT+D3ij6KIOLK6/6A/DzN4FDgIscS88GEM21he1a9iotj3V u1H/zMBux6iTBZ6YBm2iyr0MPHRw6MA= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-370-jfQBtssXPX6_DDe79gYaYw-1; Fri, 18 Mar 2022 03:04:17 -0400 X-MC-Unique: jfQBtssXPX6_DDe79gYaYw-1 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.rdu2.redhat.com [10.11.54.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 00B11802809; Fri, 18 Mar 2022 07:04:17 +0000 (UTC) Received: from T590 (ovpn-8-29.pek2.redhat.com [10.72.8.29]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 4B7E72156897; Fri, 18 Mar 2022 07:04:06 +0000 (UTC) Date: Fri, 18 Mar 2022 15:04:00 +0800 From: Ming Lei To: "yukuai (C)" Cc: Christoph Hellwig , 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> <836f0686-4ac8-327d-2bab-64a762ea8673@huawei.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-Scanned-By: MIMEDefang 2.78 on 10.11.54.6 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Mar 17, 2022 at 07:22:04PM +0800, yukuai (C) wrote: > 在 2022/03/02 8:51, Ming Lei 写道: > > On Tue, Mar 01, 2022 at 09:54:28PM +0800, yukuai (C) wrote: > > > 在 2022/03/01 18:29, Ming Lei 写道: > > > > 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: > > Hi, Ming > > Now that the above patch is landed in linux-next, do you intend to fix > the above problem? Or I can take over if you don't mind. Hi Yu Kuai, I will send one fix and your V9 later. Thanks, Ming