[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJuCfpGQK+Z0WPoRjBbSgD5m9wXyP7NJpu9fjGALmGu=6AGYaw@mail.gmail.com>
Date: Wed, 5 Jul 2023 09:14:00 -0700
From: Suren Baghdasaryan <surenb@...gle.com>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Linux regressions mailing list <regressions@...ts.linux.dev>,
"Linux regression tracking (Thorsten Leemhuis)"
<regressions@...mhuis.info>, 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, Jul 5, 2023 at 8:49 AM Andrew Morton <akpm@...ux-foundation.org> wrote:
>
> 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.
I need to make a correction to the patch fixing the issue (the first
one in the series) and will post it within an hour. Thanks!
Powered by blists - more mailing lists