From: Liam Howlett <liam.howlett@oracle.com>
To: "maple-tree@lists.infradead.org" <maple-tree@lists.infradead.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [PATCH] mm/mmap: Allow vma_expand() to lock both anon and file locks
Date: Thu, 16 Jun 2022 18:33:06 +0000 [thread overview]
Message-ID: <20220616183258.1153609-1-Liam.Howlett@oracle.com> (raw)
vma_expand() was only locking either file or anon based locks but could
unlock both. This caused a locking error in trinity fuzzer. Allow both
locks to be taken and released.
Fixes: a5985220056d (mm/mmap: use advanced maple tree API for mmap_region())
Signed-off-by: Liam R. Howlett <Liam.Howlett@oracle.com>
---
mm/mmap.c | 17 ++++++++++-------
1 file changed, 10 insertions(+), 7 deletions(-)
diff --git a/mm/mmap.c b/mm/mmap.c
index 5599c36283dd..315c3ca118cb 100644
--- a/mm/mmap.c
+++ b/mm/mmap.c
@@ -592,6 +592,11 @@ inline int vma_expand(struct ma_state *mas, struct vm_area_struct *vma,
vma_adjust_trans_huge(vma, start, end, 0);
+ if (anon_vma) {
+ anon_vma_lock_write(anon_vma);
+ anon_vma_interval_tree_pre_update_vma(vma);
+ }
+
if (file) {
mapping = file->f_mapping;
root = &mapping->i_mmap;
@@ -599,9 +604,6 @@ inline int vma_expand(struct ma_state *mas, struct vm_area_struct *vma,
i_mmap_lock_write(mapping);
flush_dcache_mmap_lock(mapping);
vma_interval_tree_remove(vma, root);
- } else if (anon_vma) {
- anon_vma_lock_write(anon_vma);
- anon_vma_interval_tree_pre_update_vma(vma);
}
vma->vm_start = start;
@@ -620,15 +622,16 @@ inline int vma_expand(struct ma_state *mas, struct vm_area_struct *vma,
__remove_shared_vm_struct(next, file, mapping);
}
+ if (file) {
+ i_mmap_unlock_write(mapping);
+ uprobe_mmap(vma);
+ }
+
if (anon_vma) {
anon_vma_interval_tree_post_update_vma(vma);
anon_vma_unlock_write(anon_vma);
}
- if (file) {
- i_mmap_unlock_write(mapping);
- uprobe_mmap(vma);
- }
if (remove_next) {
if (file) {
--
2.35.1
reply other threads:[~2022-06-16 18:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220616183258.1153609-1-Liam.Howlett@oracle.com \
--to=liam.howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=maple-tree@lists.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