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 E6B06EB64DA for ; Tue, 4 Jul 2023 16:18:39 +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:Mime-Version:References:In-Reply-To: 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=G5Wu8+feFV2bnCYz2ZTLjoUrRsJeBka/5RXV8M1Wb0Y=; b=g93E54nxjOeTjg RsTZVK7qyGrAPUpyl+zQvUwHXFpDkCGOkMfYT0l8U/cdp61Xfx762LteyOr3BJPfs+tI6cV48O7eQ R5W5UfYFb7lbRJgyKaC5iouPoSogm0bL7CEJze7OXPyLcHx5DdVVt9McnvdMFzz20If/1dT8SKE6c 5HnWr8VKI9rda2VvY2sXRKqW+KJoNQjNxJForb1abUD74GHBOA9xVOmQcmj2itrd3xzr957a+uvG7 RFG6YcDetnxcr4xXtxsooegULEhdkU1Kn07zGIxSTEPO71C/e6uqnkpGIkX30TvCHMcHMS7au1r3V 5CnfC2UujIHDbLcam/wg==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.96 #2 (Red Hat Linux)) id 1qGijF-00DnMl-1h; Tue, 04 Jul 2023 16:18:13 +0000 Received: from dfw.source.kernel.org ([139.178.84.217]) by bombadil.infradead.org with esmtps (Exim 4.96 #2 (Red Hat Linux)) id 1qGijC-00DnLY-2g for linux-arm-kernel@lists.infradead.org; Tue, 04 Jul 2023 16:18:12 +0000 Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id D45BA6129E; Tue, 4 Jul 2023 16:18:09 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id E59F5C433C7; Tue, 4 Jul 2023 16:18:08 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linux-foundation.org; s=korg; t=1688487489; bh=plFnlH3PVa4WT7JKH0cCP1otEaPsygd1p/9DKGjnZlY=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=DP+7MVF9vnt3bFNlQkpF4LExsXEbROYu+xuyqDpBQzN9EIZJgYMCQ3rRO3qj64/s5 yd/IuW/oKpDL8zTX7u+j+d8QhVQkrxzzOdnvwaPICdLx+y4LQgCKjjqcZGrfHT6/zH arQfP+r/qWPUZQdOu9jZZCWHKufOwfpShgZOVKCM= Date: Tue, 4 Jul 2023 09:18:08 -0700 From: Andrew Morton To: Greg KH Cc: Suren Baghdasaryan , Linux regressions mailing list , Bagas Sanjaya , Jacob Young , Laurent Dufour , Linux Kernel Mailing List , Linux Memory Management , Linux PowerPC , Linux ARM Subject: Re: Fwd: Memory corruption in multithreaded user space program while calling fork Message-Id: <20230704091808.aa2ed3c11a5351d9bf217ac9@linux-foundation.org> In-Reply-To: <2023070453-plod-swipe-cfbf@gregkh> References: <5c7455db-4ed8-b54f-e2d5-d2811908123d@leemhuis.info> <2023070359-evasive-regroup-f3b8@gregkh> <2023070453-plod-swipe-cfbf@gregkh> X-Mailer: Sylpheed 3.8.0beta1 (GTK+ 2.24.33; x86_64-pc-linux-gnu) Mime-Version: 1.0 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20230704_091810_923110_6F5379CF X-CRM114-Status: GOOD ( 20.37 ) 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 On Tue, 4 Jul 2023 09:00:19 +0100 Greg KH wrote: > > > > > Thanks! I'll investigate this later today. After discussing with > > > > > Andrew, we would like to disable CONFIG_PER_VMA_LOCK by default until > > > > > the issue is fixed. I'll post a patch shortly. > > > > > > > > Posted at: https://lore.kernel.org/all/20230703182150.2193578-1-surenb@google.com/ > > > > > > As that change fixes something in 6.4, why not cc: stable on it as well? > > > > Sorry, I thought since per-VMA locks were introduced in 6.4 and this > > patch is fixing 6.4 I didn't need to send it to stable for older > > versions. Did I miss something? > > 6.4.y is a stable kernel tree right now, so yes, it needs to be included > there :) I'm in wait-a-few-days-mode on this. To see if we have a backportable fix rather than disabling the feature in -stable. _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel