Received: by 2002:a05:7412:8d10:b0:f3:1519:9f41 with SMTP id bj16csp3858526rdb; Mon, 11 Dec 2023 01:56:37 -0800 (PST) X-Google-Smtp-Source: AGHT+IEmE/RJMPQKV4MgdyBJyIbC9dGlxkZMDIjDDKSOdsW84UD9WvAf9hrP0IsLd7Z79SNnslEA X-Received: by 2002:a17:903:1c6:b0:1d0:c6fd:3168 with SMTP id e6-20020a17090301c600b001d0c6fd3168mr4378212plh.55.1702288597593; Mon, 11 Dec 2023 01:56:37 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1702288597; cv=none; d=google.com; s=arc-20160816; b=dV86BG6c9wggq6kQl3Wu5aLCMCeqfE2pIetK68zpXzd4KM9zHDp8YRD4VHEFOOsEWC 0YNiDO2kbvCF0WG14y9rm92Sa84sT6DPbqVFBd68FjdkEfS8F24I+Vvcs/2OTH1mbDkg HRZCuydTzD3/JQjTIuJTH20K7GzMTffcuCTk/Auk+RjpZyDNWqQAzVjM8gAYcIgnsqGJ 8PlRVOIBHr7E1p/Yq8ySms37o23o5uQBzwn2t8OPrRW0xCpgAYoHpd9cTXeqzovEk4Wz y05RNi2hCcCI8bPyCa3xmPh/vCPnuhHhBVd6yyBL1GwP6QOmx1X8x6rsN7S0px1cXCzp YUUg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:subject:cc:to:from:date :dkim-signature; bh=8QE66EN80rR+v8XC3ABReAeepgYIkksTdkumowpdWp4=; fh=Ob/QOgXMxB1n0mGyaj2ErPiIvsxII+zaxSelQWtX4MY=; b=vupR6qqB9Q7RjTcN+tI4+DrHc7MxhmEBjrb2KD6sL6v3uuEHP6VT6qDLOiISKdb49T 9HDimwcpAogM35IFP2NVBaW0uS1VGNWNBkJUaEtq17hxUmL3lMNMxF/gAJZtJlNwcbDW 9/TSmw1z1aObz+eHyFnZ1Zyn8eqDWrIb32A22YpTTk+QsVcasf2gRk+HTu4AXZmNk6HL 20mzNPEur3/wuBtYNgeRhBLIFNojLpAjkRl+P8B65s+JHU65Amp+iZ1J5XZCkLlWZeqH P93W6IhY2YZ3kfa+yLwadAPbF+vj0UoBCJrcD3BU8/WEkIJI+cJYQGoDsTXRZ5Ee05zW p3Ag== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=n1nMQ4F7; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.38 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from fry.vger.email (fry.vger.email. [23.128.96.38]) by mx.google.com with ESMTPS id b13-20020a170902d50d00b001d0b5aa3000si6000972plg.456.2023.12.11.01.56.37 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 11 Dec 2023 01:56:37 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.38 as permitted sender) client-ip=23.128.96.38; Authentication-Results: mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=n1nMQ4F7; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.38 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: from out1.vger.email (depot.vger.email [IPv6:2620:137:e000::3:0]) by fry.vger.email (Postfix) with ESMTP id 164D38080D4E; Mon, 11 Dec 2023 01:56:35 -0800 (PST) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.103.11 at fry.vger.email Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234537AbjLKJ4W (ORCPT + 99 others); Mon, 11 Dec 2023 04:56:22 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56112 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229608AbjLKJ4V (ORCPT ); Mon, 11 Dec 2023 04:56:21 -0500 Received: from mgamail.intel.com (mgamail.intel.com [192.198.163.11]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 40A4EB7; Mon, 11 Dec 2023 01:56:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1702288588; x=1733824588; h=date:from:to:cc:subject:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=rgmW+M6hS+f0kHxkbdAPbuME2AfhGlY3DYl+PlZLxeY=; b=n1nMQ4F7jXAZ0IsdFJAjLlhoq89+wzL1Hbc6uytN1riibRa+kod+aXwE R8oqhxziDejAxTcqxr2X6frwJW0FJ7c/va6fIVUyBMeRcFI75d9sU9B4G 2c8np0OzaQqVm397TesyVbBfepJnT8uoViLc5G9xwLvvA3Op5KX1VWg8F N2JausqY0UD2+UibgoGIUrgkAcMWWiPClzsJazmQwQLo2QOkHyhIrpDBb sD5qfeiv8/TuSgMDCxP7OVLiptNIAzYca0Ahv543Bnna1NZdyIp9agGgl /5D7FjSA1L9v8DvExhWD011R3Q5DahpYb8BZKgNumZ3tOYrVPLBjbjWFf g==; X-IronPort-AV: E=McAfee;i="6600,9927,10920"; a="1434318" X-IronPort-AV: E=Sophos;i="6.04,267,1695711600"; d="scan'208";a="1434318" Received: from fmsmga004.fm.intel.com ([10.253.24.48]) by fmvoesa105.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 11 Dec 2023 01:56:28 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10920"; a="843449203" X-IronPort-AV: E=Sophos;i="6.04,267,1695711600"; d="scan'208";a="843449203" Received: from mtkaczyk-mobl.ger.corp.intel.com (HELO localhost) ([10.237.142.43]) by fmsmga004-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 11 Dec 2023 01:56:25 -0800 Date: Mon, 11 Dec 2023 10:56:20 +0100 From: Mariusz Tkaczyk To: linan666@huaweicloud.com Cc: song@kernel.org, zlliu@suse.com, neilb@suse.com, shli@fb.com, linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org, yukuai3@huawei.com, yi.zhang@huawei.com, houtao1@huawei.com, yangerkun@huawei.com Subject: Re: [PATCH] md: Don't clear MD_CLOSING when the raid is about to stop Message-ID: <20231211105620.00001753@linux.intel.com> In-Reply-To: <20231211081714.1923567-1-linan666@huaweicloud.com> References: <20231211081714.1923567-1-linan666@huaweicloud.com> X-Mailer: Claws Mail 4.1.0 (GTK 3.24.33; x86_64-w64-mingw32) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-0.8 required=5.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,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 fry.vger.email Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.4 (fry.vger.email [0.0.0.0]); Mon, 11 Dec 2023 01:56:35 -0800 (PST) On Mon, 11 Dec 2023 16:17:14 +0800 linan666@huaweicloud.com wrote: > From: Li Nan > > The raid should not be opened anymore when it is about to be stopped. > However, other processes can open it again if the flag MD_CLOSING is > cleared before exiting. From now on, this flag will not be cleared when > the raid will be stopped. > > Fixes: 065e519e71b2 ("md: MD_CLOSING needs to be cleared after called > md_set_readonly or do_md_stop") Signed-off-by: Li Nan Hello Li Nan, I was there when I needed to fix this: https://git.kernel.org/pub/scm/linux/kernel/git/song/md.git/commit/?h=md-next&id=c8870379a21fbd9ad14ca36204ccfbe9d25def43 For sure, you have to consider applying same solution for array_store "clear". Minor nit below. Thanks, Mariusz > --- > drivers/md/md.c | 8 +++----- > 1 file changed, 3 insertions(+), 5 deletions(-) > > diff --git a/drivers/md/md.c b/drivers/md/md.c > index 4e9fe5cbeedc..ebdfc9068a60 100644 > --- a/drivers/md/md.c > +++ b/drivers/md/md.c > @@ -6238,7 +6238,6 @@ static void md_clean(struct mddev *mddev) > mddev->persistent = 0; > mddev->level = LEVEL_NONE; > mddev->clevel[0] = 0; > - mddev->flags = 0; I recommend (safety recommendation): mddev->flags = MD_CLOSING; Unless you can prove that other flags cannot race. > mddev->sb_flags = 0; > mddev->ro = MD_RDWR; > mddev->metadata_type[0] = 0;