From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Jacob Young <jacobly.alt@gmail.com>
Cc: Suren Baghdasaryan <surenb@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Laurent Dufour <ldufour@linux.ibm.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Regressions <regressions@lists.linux.dev>,
Linux Memory Management <linux-mm@kvack.org>,
Linux PowerPC <linuxppc-dev@lists.ozlabs.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: Memory corruption in multithreaded user space program while calling fork
Date: Sun, 2 Jul 2023 21:11:15 +0700 [thread overview]
Message-ID: <306e4057-5e40-f0c1-d06b-2adab0eee37d@gmail.com> (raw)
In-Reply-To: <CALrpxLe2VagXEhsHPb9P4vJC97hkBYkLswFJB_jmhu1K+x_QhQ@mail.gmail.com>
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
next prev parent reply other threads:[~2023-07-02 14:11 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-02 12:27 Fwd: " Bagas Sanjaya
2023-07-02 12:40 ` Jacob Young
2023-07-02 14:11 ` Bagas Sanjaya [this message]
2023-07-03 9:53 ` Fwd: " Linux regression tracking (Thorsten Leemhuis)
2023-07-03 18:08 ` Suren Baghdasaryan
2023-07-03 18:27 ` Suren Baghdasaryan
2023-07-03 18:44 ` Greg KH
2023-07-04 7:45 ` Suren Baghdasaryan
2023-07-04 8:00 ` Greg KH
2023-07-04 16:18 ` Andrew Morton
2023-07-04 20:22 ` Suren Baghdasaryan
2023-07-04 21:28 ` Andrew Morton
2023-07-04 22:04 ` Suren Baghdasaryan
2023-07-05 6:42 ` Suren Baghdasaryan
2023-07-05 7:08 ` Greg KH
2023-07-05 8:51 ` Linux regression tracking (Thorsten Leemhuis)
2023-07-05 9:27 ` Greg KH
2023-07-05 15:49 ` Andrew Morton
2023-07-05 16:14 ` Suren Baghdasaryan
2023-07-05 17:17 ` Suren Baghdasaryan
2023-07-08 11:35 ` Thorsten Leemhuis
2023-07-08 17:29 ` Linus Torvalds
2023-07-08 17:39 ` Andrew Morton
2023-07-08 18:04 ` Linus Torvalds
2023-07-08 18:40 ` Suren Baghdasaryan
2023-07-08 19:05 ` Linus Torvalds
2023-07-08 19:17 ` Suren Baghdasaryan
2023-07-08 19:22 ` Linus Torvalds
2023-07-08 19:41 ` Suren Baghdasaryan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=306e4057-5e40-f0c1-d06b-2adab0eee37d@gmail.com \
--to=bagasdotme@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=jacobly.alt@gmail.com \
--cc=ldufour@linux.ibm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=regressions@lists.linux.dev \
--cc=surenb@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox