From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: stable@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
patches@lists.linux.dev, John Hsu <John.Hsu@mediatek.com>,
linux-mm@kvack.org, "Liam R. Howlett" <Liam.Howlett@oracle.com>
Subject: [PATCH 6.1 576/591] mm/mmap: Fix extra maple tree write
Date: Sun, 16 Jul 2023 21:51:55 +0200 [thread overview]
Message-ID: <20230716194938.761629385@linuxfoundation.org> (raw)
In-Reply-To: <20230716194923.861634455@linuxfoundation.org>
From: "Liam R. Howlett" <Liam.Howlett@oracle.com>
based on commit 0503ea8f5ba73eb3ab13a81c1eefbaf51405385a upstream.
This was inadvertently fixed during the removal of __vma_adjust().
When __vma_adjust() is adjusting next with a negative value (pushing
vma->vm_end lower), there would be two writes to the maple tree. The
first write is unnecessary and uses all allocated nodes in the maple
state. The second write is necessary but will need to allocate nodes
since the first write has used the allocated nodes. This may be a
problem as it may not be safe to allocate at this time, such as a low
memory situation. Fix the issue by avoiding the first write and only
write the adjusted "next" VMA.
Reported-by: John Hsu <John.Hsu@mediatek.com>
Link: https://lore.kernel.org/lkml/9cb8c599b1d7f9c1c300d1a334d5eb70ec4d7357.camel@mediatek.com/
Cc: stable@vger.kernel.org
Cc: linux-mm@kvack.org
Signed-off-by: Liam R. Howlett <Liam.Howlett@oracle.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
---
mm/mmap.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
--- a/mm/mmap.c
+++ b/mm/mmap.c
@@ -767,7 +767,8 @@ int __vma_adjust(struct vm_area_struct *
}
if (end != vma->vm_end) {
if (vma->vm_end > end) {
- if (!insert || (insert->vm_start != end)) {
+ if ((vma->vm_end + adjust_next != end) &&
+ (!insert || (insert->vm_start != end))) {
vma_mas_szero(&mas, end, vma->vm_end);
mas_reset(&mas);
VM_WARN_ON(insert &&
next prev parent reply other threads:[~2023-07-16 20:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-16 19:42 [PATCH 6.1 000/591] 6.1.39-rc1 review Greg Kroah-Hartman
2023-07-16 19:43 ` [PATCH 6.1 075/591] sctp: add bpf_bypass_getsockopt proto callback Greg Kroah-Hartman
2023-07-16 19:51 ` Greg Kroah-Hartman [this message]
2023-07-16 23:40 ` [PATCH 6.1 000/591] 6.1.39-rc1 review Daniel Díaz
2023-07-17 0:01 ` Guenter Roeck
2023-07-17 18:47 ` Greg Kroah-Hartman
2023-07-17 0:47 ` ogasawara takeshi
2023-07-17 11:18 ` Conor Dooley
2023-07-17 20:46 ` Shuah Khan
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=20230716194938.761629385@linuxfoundation.org \
--to=gregkh@linuxfoundation.org \
--cc=John.Hsu@mediatek.com \
--cc=Liam.Howlett@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=patches@lists.linux.dev \
--cc=stable@vger.kernel.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