[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20230705084906.22eee41e6e72da588fce5a48@linux-foundation.org>
Date: Wed, 5 Jul 2023 08:49:06 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Linux regressions mailing list <regressions@...ts.linux.dev>
Cc: "Linux regression tracking (Thorsten Leemhuis)"
<regressions@...mhuis.info>,
Suren Baghdasaryan <surenb@...gle.com>,
Bagas Sanjaya <bagasdotme@...il.com>,
Jacob Young <jacobly.alt@...il.com>,
Laurent Dufour <ldufour@...ux.ibm.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Memory Management <linux-mm@...ck.org>,
Linux PowerPC <linuxppc-dev@...ts.ozlabs.org>,
Linux ARM <linux-arm-kernel@...ts.infradead.org>,
Greg KH <gregkh@...uxfoundation.org>
Subject: Re: Fwd: Memory corruption in multithreaded user space program
while calling fork
On Wed, 5 Jul 2023 10:51:57 +0200 "Linux regression tracking (Thorsten Leemhuis)" <regressions@...mhuis.info> 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.
Powered by blists - more mailing lists