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 bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id DB301C43217 for ; Mon, 9 May 2022 10:16:12 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=GgRX9hAkxMqbWYYQeIb4fDwISIuQVvS15S1DEbW2LwM=; b=3h6ZLuGVppC+Hh oKyoKY+TDaxoDmzvaqq34oaui2YuGjag/nGApVhhFSrfPGztlt5Fy8adFrVip87UBqnwYyk+xgf4q k0lC64vr7kxFk5UFRxZfF2HDIC+i9EYa6luMCWOD6X5EcgtCVsocbpx6p+veZvk0Aykz5cD2JKcuc VwdnvT6B7UOXUgwUHk1rCi1kB7gQ3Eu7dwE4POSEBgsPmLEq9v3zqmtP/e5tnmri7LwVSbOQJAsbs 6kk2NzCt4P+u/nk6wGcrpBSP9oCVrzKX61Mw46KXKvM/vX30X5ZLffhctTHJd6cMJIB6e5g1SbIWo N4gmIbATFXp77HKRONCA==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1no0Pr-00DhrZ-3U; Mon, 09 May 2022 10:14:59 +0000 Received: from sin.source.kernel.org ([2604:1380:40e1:4800::1]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1no0Po-00Dhq0-06 for linux-arm-kernel@lists.infradead.org; Mon, 09 May 2022 10:14:57 +0000 Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by sin.source.kernel.org (Postfix) with ESMTPS id 4DC6CCE13C4; Mon, 9 May 2022 10:14:52 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 729AEC385AB; Mon, 9 May 2022 10:14:49 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1652091290; bh=+9srvDHqiWKm6OjKS3qVUqzfohs6qxQD/zq2WlbkEa0=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=z7vtLfTH8SA1J3f2yk0yw/6kQ1lAOH0G7IygugS0czPnxCS71yOLEDkH9PKXy1in/ PshnArIMLgpNvDyeaVZIyWVAGJn5J67zPbng2Cu+rjP7yWCDRKdyHzx1SaHITM5mB4 UQmrOxirfZMwsX7gnCdghtChxLaLJI+zMEpL/yGI= Date: Mon, 9 May 2022 12:14:46 +0200 From: Greg KH To: Chen Zhongjin Cc: linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-arch@vger.kernel.org, stable@vger.kernel.org, peterz@infradead.org, tglx@linutronix.de, namit@vmware.com, gor@linux.ibm.com, rdunlap@infradead.org, sashal@kernel.org Subject: Re: [PATCH 5.10 v3] locking/csd_lock: fix csdlock_debug cause arm64 boot panic Message-ID: References: <20220507084510.14761-1-chenzhongjin@huawei.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20220509_031456_263950_91389AE9 X-CRM114-Status: GOOD ( 21.16 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org A: http://en.wikipedia.org/wiki/Top_post Q: Were do I find info about this thing called top-posting? A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? A: No. Q: Should I include quotations after my reply? http://daringfireball.net/2007/07/on_top On Mon, May 09, 2022 at 11:14:12AM +0800, Chen Zhongjin wrote: > Hi Greg, > > Since the patch: > https://lore.kernel.org/all/20210420093559.23168-1-catalin.marinas@arm.com/ > has forced CONFIG_SPARSEMEM_VMEMMAP=y from 5.12, it's not necessary to include > this patch on master. > > However this problem still exist on 5.10 stable, so either we can backport the > above patch to 5.10, or independently apply mine. > > I'm not sure if backporting one exist patch is better, but that patch only > changed configs without any fix for old builds. > > If you have any advice please tell me. If you want to include a patch in the stable tree that is NOT in Linus's tree, then you need to document it very very well as to why this is not the case. If backporting the above commit is better, I would much rather do that, please ask the maintainers and developers of it if they will do that. thanks, greg k-h _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel