Thread (29 messages) 29 messages, 7 authors, 2023-07-08

Re: Fwd: Memory corruption in multithreaded user space program while calling fork

From: Andrew Morton <akpm@linux-foundation.org>
Date: 2023-07-04 16:18:15
Also in: linux-arm-kernel, linux-mm, lkml, regressions

On Tue, 4 Jul 2023 09:00:19 +0100 Greg KH [off-list ref] wrote:
quoted
quoted
quoted
quoted
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/ (local)
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.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help