From: "Edgecombe, Rick P" <rick.p.edgecombe@intel.com>
To: "Liam.Howlett@oracle.com" <Liam.Howlett@oracle.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3/3] mm/mmap: Regression fix for unmapped_area{_topdown}
Date: Fri, 14 Apr 2023 16:27:15 +0000 [thread overview]
Message-ID: <3bf69efaeddae3599a6d7ea8a225f64066811473.camel@intel.com> (raw)
In-Reply-To: <20230414145728.4067069-3-Liam.Howlett@oracle.com>
On Fri, 2023-04-14 at 10:57 -0400, Liam R. Howlett wrote:<br>
> + tmp = mas_next(&mas, ULONG_MAX);
> + if (tmp && (tmp->vm_flags & VM_GROWSDOWN)) {
Why also check VM_GROWSDOWN here (and VM_GROWSUP below)?
vm_start/end_gap() already have checks inside.
> + if (vm_start_gap(tmp) < gap + length - 1) {
> + low_limit = tmp->vm_end;
> + mas_reset(&mas);
> + goto retry;
> + }
> + } else {
> + tmp = mas_prev(&mas, 0);
> + if (tmp && (tmp->vm_flags & VM_GROWSUP) &&
> + vm_end_gap(tmp) > gap) {
> + low_limit = vm_end_gap(tmp);
> + mas_reset(&mas);
> + goto retry;
> + }
> + }
> +
Could it be like this?
tmp = mas_next(&mas, ULONG_MAX);
if (tmp && vm_start_gap(tmp) < gap + length - 1) {
low_limit = tmp->vm_end;
mas_reset(&mas);
goto retry;
}
} else {
tmp = mas_prev(&mas, 0);
if (tmp && vm_end_gap(tmp) > gap) {
low_limit = vm_end_gap(tmp);
mas_reset(&mas);
goto retry;
}
}
next prev parent reply other threads:[~2023-04-14 16:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-14 14:57 [PATCH 1/3] maple_tree: Make maple state reusable after mas_empty_area_rev() Liam R. Howlett
2023-04-14 14:57 ` [PATCH 2/3] maple_tree: Fix mas_empty_area() search Liam R. Howlett
2023-04-14 14:57 ` [PATCH 3/3] mm/mmap: Regression fix for unmapped_area{_topdown} Liam R. Howlett
2023-04-14 16:27 ` Edgecombe, Rick P [this message]
2023-04-14 17:26 ` Liam R. Howlett
2023-04-14 17:29 ` Liam R. Howlett
2023-04-14 17:53 ` Edgecombe, Rick P
2023-04-14 18:07 ` Liam R. Howlett
2023-04-14 18:21 ` Edgecombe, Rick P
2023-04-14 18:59 ` [PATCH v2] " Liam R. Howlett
2023-04-14 19:09 ` Andrew Morton
2023-04-29 14:32 ` Tad
2023-04-30 22:41 ` Michael Keyes
2023-05-02 14:08 ` Liam R. Howlett
2023-05-02 14:09 ` Liam R. Howlett
2023-05-15 8:57 ` Juhyung Park
2023-05-15 14:36 ` Liam R. Howlett
2023-04-19 9:02 ` [PATCH 1/3] maple_tree: Make maple state reusable after mas_empty_area_rev() Peng Zhang
2023-04-19 22:54 ` Liam R. Howlett
2023-04-20 4:21 ` Peng Zhang
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=3bf69efaeddae3599a6d7ea8a225f64066811473.camel@intel.com \
--to=rick.p.edgecombe@intel.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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