From: Suren Baghdasaryan <surenb@google.com>
To: torvalds@linux-foundation.org
Cc: jacobly.alt@gmail.com, regressions@lists.linux.dev,
"Jiri Slaby" <jirislaby@kernel.org>,
david@redhat.com, gregkh@linuxfoundation.org,
linux-kernel@vger.kernel.org, liam.howlett@oracle.com,
"Suren Baghdasaryan" <surenb@google.com>,
linux-mm@kvack.org, peterx@redhat.com, regressions@leemhuis.info,
willy@infradead.org, bagasdotme@gmail.com,
stable@vger.kernel.org, akpm@linux-foundation.org,
ldufour@linux.ibm.com, linuxppc-dev@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org,
"Holger Hoffstätte" <holger@applied-asynchrony.com>
Subject: [PATCH v2 3/3] fork: lock VMAs of the parent process when forking
Date: Sat, 8 Jul 2023 12:12:12 -0700 [thread overview]
Message-ID: <20230708191212.4147700-3-surenb@google.com> (raw)
In-Reply-To: <20230708191212.4147700-1-surenb@google.com>
When forking a child process, parent write-protects an anonymous page
and COW-shares it with the child being forked using copy_present_pte().
Parent's TLB is flushed right before we drop the parent's mmap_lock in
dup_mmap(). If we get a write-fault before that TLB flush in the parent,
and we end up replacing that anonymous page in the parent process in
do_wp_page() (because, COW-shared with the child), this might lead to
some stale writable TLB entries targeting the wrong (old) page.
Similar issue happened in the past with userfaultfd (see flush_tlb_page()
call inside do_wp_page()).
Lock VMAs of the parent process when forking a child, which prevents
concurrent page faults during fork operation and avoids this issue.
This fix can potentially regress some fork-heavy workloads. Kernel build
time did not show noticeable regression on a 56-core machine while a
stress test mapping 10000 VMAs and forking 5000 times in a tight loop
shows ~5% regression. If such fork time regression is unacceptable,
disabling CONFIG_PER_VMA_LOCK should restore its performance. Further
optimizations are possible if this regression proves to be problematic.
Suggested-by: David Hildenbrand <david@redhat.com>
Reported-by: Jiri Slaby <jirislaby@kernel.org>
Closes: https://lore.kernel.org/all/dbdef34c-3a07-5951-e1ae-e9c6e3cdf51b@kernel.org/
Reported-by: Holger Hoffstätte <holger@applied-asynchrony.com>
Closes: https://lore.kernel.org/all/b198d649-f4bf-b971-31d0-e8433ec2a34c@applied-asynchrony.com/
Reported-by: Jacob Young <jacobly.alt@gmail.com>
Closes: https://bugzilla.kernel.org/show_bug.cgi?id=217624
Fixes: 0bff0aaea03e ("x86/mm: try VMA lock-based page fault handling first")
Cc: stable@vger.kernel.org
Signed-off-by: Suren Baghdasaryan <surenb@google.com>
---
kernel/fork.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/kernel/fork.c b/kernel/fork.c
index b85814e614a5..d2e12b6d2b18 100644
--- a/kernel/fork.c
+++ b/kernel/fork.c
@@ -686,6 +686,7 @@ static __latent_entropy int dup_mmap(struct mm_struct *mm,
for_each_vma(old_vmi, mpnt) {
struct file *file;
+ vma_start_write(mpnt);
if (mpnt->vm_flags & VM_DONTCOPY) {
vm_stat_account(mm, mpnt->vm_flags, -vma_pages(mpnt));
continue;
--
2.41.0.390.g38632f3daf-goog
next prev parent reply other threads:[~2023-07-08 19:14 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-08 19:12 [PATCH v2 1/3] mm: lock a vma before stack expansion Suren Baghdasaryan
2023-07-08 19:12 ` [PATCH v2 2/3] mm: lock newly mapped VMA which can be modified after it becomes visible Suren Baghdasaryan
2023-07-08 19:12 ` Suren Baghdasaryan [this message]
2023-07-08 19:22 ` [PATCH v2 3/3] fork: lock VMAs of the parent process when forking Suren Baghdasaryan
2023-07-08 21:18 ` Linus Torvalds
2023-07-08 22:36 ` Suren Baghdasaryan
2023-07-08 22:53 ` Linus Torvalds
2023-07-08 23:03 ` Suren Baghdasaryan
2023-08-04 21:46 ` Mateusz Guzik
2023-08-04 22:49 ` Linus Torvalds
2023-08-04 23:25 ` Mateusz Guzik
2023-08-05 0:14 ` Linus Torvalds
2023-08-05 0:26 ` Suren Baghdasaryan
2023-08-05 0:34 ` Suren Baghdasaryan
2023-08-05 0:49 ` Mateusz Guzik
2023-08-05 1:06 ` Suren Baghdasaryan
2023-08-05 1:16 ` Mateusz Guzik
2023-08-05 1:36 ` Suren Baghdasaryan
2023-08-05 1:06 ` Mateusz Guzik
2023-08-05 1:42 ` Suren Baghdasaryan
2023-08-09 21:07 ` Mateusz Guzik
2023-08-10 20:31 ` 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=20230708191212.4147700-3-surenb@google.com \
--to=surenb@google.com \
--cc=akpm@linux-foundation.org \
--cc=bagasdotme@gmail.com \
--cc=david@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=holger@applied-asynchrony.com \
--cc=jacobly.alt@gmail.com \
--cc=jirislaby@kernel.org \
--cc=ldufour@linux.ibm.com \
--cc=liam.howlett@oracle.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=peterx@redhat.com \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=willy@infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).