[<prev] [next>] [day] [month] [year] [list]
Message-ID: <306e4057-5e40-f0c1-d06b-2adab0eee37d@gmail.com>
Date: Sun, 2 Jul 2023 21:11:15 +0700
From: Bagas Sanjaya <bagasdotme@...il.com>
To: Jacob Young <jacobly.alt@...il.com>
Cc: Suren Baghdasaryan <surenb@...gle.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Laurent Dufour <ldufour@...ux.ibm.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Regressions <regressions@...ts.linux.dev>,
Linux Memory Management <linux-mm@...ck.org>,
Linux PowerPC <linuxppc-dev@...ts.ozlabs.org>,
Linux ARM <linux-arm-kernel@...ts.infradead.org>
Subject: Re: Memory corruption in multithreaded user space program while
calling fork
On 7/2/23 19:40, Jacob Young wrote:
>> Jacob: Can you repeat bisection please? Why did you skip VMA lock-based
> page fault commits in your bisection?
>
> All skips were due to compile errors of the form:
> make[3]: 'install_headers' is up to date.
> In file included from ./include/linux/memcontrol.h:20,
> from ./include/linux/swap.h:9,
> from ./include/linux/suspend.h:5,
> from arch/x86/kernel/asm-offsets.c:14:
> ./include/linux/mm.h: In function ‘vma_try_start_write’:
> ./include/linux/mm.h:702:37: error: ‘struct vm_area_struct’ has no member named ‘vm_lock’
> 702 | if (!down_write_trylock(&vma->vm_lock->lock))
> | ^~
> ./include/linux/mm.h:706:22: error: ‘struct vm_area_struct’ has no member named ‘vm_lock’
> 706 | up_write(&vma->vm_lock->lock);
> | ^~
> make[1]: *** [scripts/Makefile.build:114: arch/x86/kernel/asm-offsets.s] Error 1
> make: *** [Makefile:1286: prepare0] Error 2
>
1. Please don't send HTML emails as mailing lists reject them.
2. Reply inline with appropriate context, rather than top-post reply.
--
An old man doll... just what I always wanted! - Clara
Powered by blists - more mailing lists