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 lists.ozlabs.org (lists.ozlabs.org [112.213.38.117]) (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 1E66FEB64DA for ; Wed, 5 Jul 2023 15:50:08 +0000 (UTC) Authentication-Results: lists.ozlabs.org; dkim=fail reason="signature verification failed" (1024-bit key; unprotected) header.d=linux-foundation.org header.i=@linux-foundation.org header.a=rsa-sha256 header.s=korg header.b=fG4XT65n; dkim-atps=neutral Received: from boromir.ozlabs.org (localhost [IPv6:::1]) by lists.ozlabs.org (Postfix) with ESMTP id 4Qx3yQ4Fz6z3bjw for ; Thu, 6 Jul 2023 01:50:06 +1000 (AEST) Authentication-Results: lists.ozlabs.org; dkim=pass (1024-bit key; unprotected) header.d=linux-foundation.org header.i=@linux-foundation.org header.a=rsa-sha256 header.s=korg header.b=fG4XT65n; dkim-atps=neutral Authentication-Results: lists.ozlabs.org; spf=pass (sender SPF authorized) smtp.mailfrom=linux-foundation.org (client-ip=2604:1380:4641:c500::1; helo=dfw.source.kernel.org; envelope-from=akpm@linux-foundation.org; receiver=lists.ozlabs.org) Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 4Qx3xP5l9Hz30Jy for ; Thu, 6 Jul 2023 01:49:12 +1000 (AEST) 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 8E55D61342; Wed, 5 Jul 2023 15:49:08 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 93E63C433C7; Wed, 5 Jul 2023 15:49:07 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linux-foundation.org; s=korg; t=1688572148; bh=wUQaHnYHUwnVipBpt2LgwmRDolTVE3ThEDGnTGR+Eds=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=fG4XT65n6cKnLJenjLqQmGWEBlAiyjkMKt0HSpYaUV5eR2EHSpIgV0SOmzYSapEc3 7LXqOIeoCOXNXSWuuaxx3BN+jUfYb/G5r213KO5LsowSdYtl+rA0e7BctzdnCsKY+d btp/WMyfyUG/4qN91o+MTZq7O12MH+TLIfEZM4rE= Date: Wed, 5 Jul 2023 08:49:06 -0700 From: Andrew Morton To: Linux regressions mailing list Subject: Re: Fwd: Memory corruption in multithreaded user space program while calling fork Message-Id: <20230705084906.22eee41e6e72da588fce5a48@linux-foundation.org> In-Reply-To: <7668c45a-70b1-dc2f-d0f5-c0e76ec17145@leemhuis.info> References: <5c7455db-4ed8-b54f-e2d5-d2811908123d@leemhuis.info> <2023070359-evasive-regroup-f3b8@gregkh> <2023070453-plod-swipe-cfbf@gregkh> <20230704091808.aa2ed3c11a5351d9bf217ac9@linux-foundation.org> <2023070509-undertow-pulverize-5adc@gregkh> <7668c45a-70b1-dc2f-d0f5-c0e76ec17145@leemhuis.info> X-Mailer: Sylpheed 3.8.0beta1 (GTK+ 2.24.33; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: linuxppc-dev@lists.ozlabs.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Jacob Young , Linux PowerPC , Linux Kernel Mailing List , Linux Memory Management , "Linux regression tracking \(Thorsten Leemhuis\)" , Bagas Sanjaya , Greg KH , Laurent Dufour , Suren Baghdasaryan , Linux ARM Errors-To: linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Sender: "Linuxppc-dev" On Wed, 5 Jul 2023 10:51:57 +0200 "Linux regression tracking (Thorsten Leemhuis)" wrote: > >>> 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. > > Andrew, how long will you remain in "wait-a-few-days-mode"? Given what > Greg said below and that we already had three reports I know of I'd > prefer if we could fix this rather sooner than later in mainline -- > especially as Arch Linux and openSUSE Tumbleweed likely have switched to > 6.4.y already or will do so soon. I'll send today's 2-patch series to Linus today or tomorrow.