On Tue, Dec 14, 2021 at 05:52:54PM -0500, Michael Pratt wrote: > On Tue, Dec 14, 2021 at 1:06 PM Michael Pratt <mpratt%google.com@localhost> wrote: > > > > [This is a reply to > > https://mail-index.netbsd.org/tech-kern/2021/12/01/msg027830.html. I > > just joined the mailing list and can't seem to find the metadata > > required for a proper reply. Apologies.] > > > > I filed https://gnats.netbsd.org/56535 for this a while ago, which has > > an even simpler reproducer: a direct fork() call with a child that > > immediately exits sometimes causes memory corruption in the parent > > process. > > > > We've kept looking since filing https://gnats.netbsd.org/56535 but > > haven't had luck on further simplification. No C reproducer yet, > > unfortunately. (No crashes if the Go parent process is single-threaded > > either.) > > I spoke too soon here, we managed to get a reproducer in C today, > which I've posted at > https://github.com/golang/go/issues/34988#issuecomment-994115345. I can confirm it corrupts here too on my "AMD Ryzen 9 3900X 12-Core Processor" (on bare metal) when I run multiple instances in parallel on NetBSD 9.99.92. Reinoud
Attachment:
signature.asc
Description: PGP signature