From: Vlastimil Babka <vbabka@suse.cz>
To: linux-mm@kvack.org, "Liam R. Howlett" <Liam.Howlett@oracle.com>
Cc: linux-kernel@vger.kernel.org, patches@lists.linux.dev,
maple-tree@lists.infradead.org, Vlastimil Babka <vbabka@suse.cz>
Subject: [RFC 02/11] mm/mmap/vma_merge: use only primary pointers for preparing merge
Date: Fri, 24 Feb 2023 11:00:13 +0100 [thread overview]
Message-ID: <20230224100022.11268-3-vbabka@suse.cz> (raw)
In-Reply-To: <20230224100022.11268-1-vbabka@suse.cz>
In the merging preparation part of vma_merge(), some vma pointer
variables are assigned for later execution of the merge, but also read
from in the block itself. The code is easier follow and check against
the cases diagram in the comment if the code reads only from the
"primary" vma variables prev, mid, next instead. No functional change.
Signed-off-by: Vlastimil Babka <vbabka@suse.cz>
---
mm/mmap.c | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/mm/mmap.c b/mm/mmap.c
index 740b54be3ed4..0a8b052e3022 100644
--- a/mm/mmap.c
+++ b/mm/mmap.c
@@ -950,16 +950,16 @@ struct vm_area_struct *vma_merge(struct vma_iterator *vmi, struct mm_struct *mm,
is_mergeable_anon_vma(prev->anon_vma, next->anon_vma, NULL)) {
remove = mid; /* case 1 */
vma_end = next->vm_end;
- err = dup_anon_vma(res, remove);
+ err = dup_anon_vma(prev, mid);
if (mid != next) { /* case 6 */
remove2 = next;
- if (!remove->anon_vma)
- err = dup_anon_vma(res, remove2);
+ if (!mid->anon_vma)
+ err = dup_anon_vma(prev, next);
}
} else if (merge_prev) {
err = 0; /* case 2 */
if (mid && end > mid->vm_start) {
- err = dup_anon_vma(res, mid);
+ err = dup_anon_vma(prev, mid);
if (end == mid->vm_end) { /* case 7 */
remove = mid;
} else { /* case 5 */
@@ -972,8 +972,8 @@ struct vm_area_struct *vma_merge(struct vma_iterator *vmi, struct mm_struct *mm,
if (prev && addr < prev->vm_end) { /* case 4 */
vma_end = addr;
adjust = mid;
- adj_next = -(vma->vm_end - addr);
- err = dup_anon_vma(adjust, prev);
+ adj_next = -(prev->vm_end - addr);
+ err = dup_anon_vma(mid, prev);
} else {
vma = next; /* case 3 */
vma_start = addr;
@@ -982,7 +982,7 @@ struct vm_area_struct *vma_merge(struct vma_iterator *vmi, struct mm_struct *mm,
err = 0;
if (mid != next) { /* case 8 */
remove = mid;
- err = dup_anon_vma(res, remove);
+ err = dup_anon_vma(next, mid);
}
}
}
--
2.39.2
next prev parent reply other threads:[~2023-02-24 10:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-24 10:00 [RFC 00/11] cleanup vma_merge and improve mergeability tests Vlastimil Babka
2023-02-24 10:00 ` [RFC 01/11] mm/mremap: fix dup_anon_vma() in vma_merge() case 4 Vlastimil Babka
2023-02-24 10:00 ` Vlastimil Babka [this message]
2023-02-24 10:00 ` [RFC 03/11] mm/mmap/vma_merge: use the proper vma pointer in case 3 Vlastimil Babka
2023-02-24 10:00 ` [RFC 04/11] mm/mmap/vma_merge: use the proper vma pointers in cases 1 and 6 Vlastimil Babka
2023-02-24 10:00 ` [RFC 05/11] mm/mmap/vma_merge: use the proper vma pointer in case 4 Vlastimil Babka
2023-02-24 10:00 ` [RFC 06/11] mm/mmap/vma_merge: initialize mid and next in natural order Vlastimil Babka
2023-02-24 10:00 ` [RFC 07/11] mm/mmap/vma_merge: set mid to NULL if not applicable Vlastimil Babka
2023-02-24 10:00 ` [RFC 08/11] mm/mmap/vma_merge: rename adj_next to adj_start Vlastimil Babka
2023-02-24 10:00 ` [RFC 09/11] mm/mmap/vma_merge: convert mergeability checks to return bool Vlastimil Babka
2023-02-24 10:00 ` [RFC 10/11] mm/mmap: start distinguishing if vma can be removed in mergeability test Vlastimil Babka
2023-02-24 10:00 ` [RFC 11/11] mm/mremap: simplify vma expansion again Vlastimil Babka
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=20230224100022.11268-3-vbabka@suse.cz \
--to=vbabka@suse.cz \
--cc=Liam.Howlett@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=maple-tree@lists.infradead.org \
--cc=patches@lists.linux.dev \
/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).