From: Marco Vanotti <mvanotti@google.com>
To: Brian Geffon <bgeffon@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
Jann Horn <jannh@google.com>, Vlastimil Babka <vbabka@suse.cz>,
"Liam R. Howlett" <Liam.Howlett@oracle.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 1/5] mm: mremap: Fix new_addr being used as a hint with MREMAP_DONTUNMAP
Date: Wed, 11 Dec 2024 13:46:17 -0300 [thread overview]
Message-ID: <CADMPHGtENiESdnHsoMCsVA2FNBg4jLS4kMZJfGOmvv7=9k_+HA@mail.gmail.com> (raw)
In-Reply-To: <20241210213050.2839638-2-bgeffon@google.com>
[-- Attachment #1: Type: text/plain, Size: 3386 bytes --]
On Tue, Dec 10, 2024 at 6:31 PM Brian Geffon <bgeffon@google.com> wrote:
>
> Two non-mutually exclusive paths can land in mremap_to, MREMAP_FIXED
> and MREMAP_DONTUNMAP which are called from mremap(). In the case of
> MREMAP_FIXED we must validate the new_addr to ensure that the new
> address is valid. In the case of MREMAP_DONTUNMAP without MREMAP_FIXED
> a new address is specified as a hint, just like it would be in the
> case of mmap. In this second case we don't need to perform any checks
> because get_unmapped_area() will align new_addr, just like it would in
> the case of mmap.
>
> This patch only fixes the behavior that was inadvertently added
> with MREMAP_DONTUNMAP.
>
> v2:
> - Addressed comment from Marco Vanotti to consolidate these checks
> into existing MREMAP_FIXED blocks.
>
> Signed-off-by: Brian Geffon <bgeffon@google.com>
> Reported-by: Marco Vanotti <mvanotti@google.com>
Reviewed-By: Marco Vanotti <mvanotti@google.com>
> ---
> mm/mremap.c | 29 +++++++++++++++++++----------
> 1 file changed, 19 insertions(+), 10 deletions(-)
>
> diff --git a/mm/mremap.c b/mm/mremap.c
> index 60473413836b..62aec72bbe42 100644
> --- a/mm/mremap.c
> +++ b/mm/mremap.c
> @@ -912,16 +912,6 @@ static unsigned long mremap_to(unsigned long addr, unsigned long old_len,
> unsigned long ret;
> unsigned long map_flags = 0;
>
> - if (offset_in_page(new_addr))
> - return -EINVAL;
> -
> - if (new_len > TASK_SIZE || new_addr > TASK_SIZE - new_len)
> - return -EINVAL;
> -
> - /* Ensure the old/new locations do not overlap */
> - if (addr + old_len > new_addr && new_addr + new_len > addr)
> - return -EINVAL;
> -
> /*
> * move_vma() need us to stay 4 maps below the threshold, otherwise
> * it will bail out at the very beginning.
> @@ -940,6 +930,25 @@ static unsigned long mremap_to(unsigned long addr, unsigned long old_len,
> return -ENOMEM;
>
> if (flags & MREMAP_FIXED) {
> + /*
> + * Two non-mutually exclusive paths can land in mremap_to, MREMAP_FIXED
> + * and MREMAP_DONTUNMAP which are called from mremap(). In the case of
> + * MREMAP_FIXED we must validate the new_addr to ensure that the new
> + * address is valid. In the case of MREMAP_DONTUNMAP without MREMAP_FIXED
> + * a new address is specified as a hint, just like it would be in the
> + * case of mmap. In this second case we don't need to perform any checks
> + * because get_unmapped_area() will align new_addr, just like it would in
> + * the case of mmap.
> + */
> + if (offset_in_page(new_addr))
> + return -EINVAL;
> +
> + if (new_len > TASK_SIZE || new_addr > TASK_SIZE - new_len)
> + return -EINVAL;
> +
> + /* Ensure the old/new locations do not overlap */
> + if (addr + old_len > new_addr && new_addr + new_len > addr)
> + return -EINVAL;
> /*
> * In mremap_to().
> * VMA is moved to dst address, and munmap dst first.
> --
> 2.47.0.338.g60cca15819-goog
>
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 5294 bytes --]
next prev parent reply other threads:[~2024-12-11 16:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-10 21:30 [RFC PATCH 0/5] mm: Fix mremap behavior when using addr hints Brian Geffon
2024-12-10 21:30 ` [RFC PATCH 1/5] mm: mremap: Fix new_addr being used as a hint with MREMAP_DONTUNMAP Brian Geffon
2024-12-11 16:46 ` Marco Vanotti [this message]
2024-12-10 21:30 ` [RFC PATCH 2/5] mm: mremap: Use round_hint_to_min() for new_addr hints Brian Geffon
2024-12-10 21:30 ` [RFC PATCH 3/5] mm: mremap: Allow new_addr to be specified as a hint Brian Geffon
2024-12-11 20:34 ` Brian Geffon
2024-12-10 21:30 ` [RFC PATCH 4/5] selftests: mm: Add a new MREMAP_DONTUNMAP self test Brian Geffon
2024-12-10 21:30 ` [RFC PATCH 5/5] selftests: mm: Add selftest for new_addr hint with MREMAP_MAYMOVE Brian Geffon
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='CADMPHGtENiESdnHsoMCsVA2FNBg4jLS4kMZJfGOmvv7=9k_+HA@mail.gmail.com' \
--to=mvanotti@google.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=bgeffon@google.com \
--cc=jannh@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=vbabka@suse.cz \
/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