From: Michal Hocko <mhocko@suse.com>
To: "Joel Fernandes (Google)" <joel@joelfernandes.org>
Cc: linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-mm@kvack.org, Shuah Khan <shuah@kernel.org>,
Vlastimil Babka <vbabka@suse.cz>,
Linus Torvalds <torvalds@linux-foundation.org>,
Lorenzo Stoakes <lstoakes@gmail.com>,
Kirill A Shutemov <kirill@shutemov.name>,
"Liam R. Howlett" <liam.howlett@oracle.com>,
"Paul E. McKenney" <paulmck@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Kalesh Singh <kaleshsingh@google.com>,
Lokesh Gidra <lokeshgidra@google.com>
Subject: Re: [PATCH v6 2/7] mm/mremap: Allow moves within the same VMA for stack moves
Date: Fri, 8 Sep 2023 15:11:09 +0200 [thread overview]
Message-ID: <ZPsdbUM9J3LPVDfq@dhcp22.suse.cz> (raw)
In-Reply-To: <20230903151328.2981432-3-joel@joelfernandes.org>
On Sun 03-09-23 15:13:23, Joel Fernandes wrote:
> For the stack move happening in shift_arg_pages(), the move is happening
> within the same VMA which spans the old and new ranges.
>
> In case the aligned address happens to fall within that VMA, allow such
> moves and don't abort the mremap alignment optimization.
>
> In the regular non-stack mremap case, we cannot allow any such moves as
> will end up destroying some part of the mapping (either the source of
> the move, or part of the existing mapping). So just avoid it for stack
> moves.
>
> Signed-off-by: Joel Fernandes (Google) <joel@joelfernandes.org>
LGTM
Acked-by: Michal Hocko <mhocko@suse.com>
Thanks!
> ---
> fs/exec.c | 2 +-
> include/linux/mm.h | 2 +-
> mm/mremap.c | 33 +++++++++++++++++++--------------
> 3 files changed, 21 insertions(+), 16 deletions(-)
>
> diff --git a/fs/exec.c b/fs/exec.c
> index 1a827d55ba94..244925307958 100644
> --- a/fs/exec.c
> +++ b/fs/exec.c
> @@ -712,7 +712,7 @@ static int shift_arg_pages(struct vm_area_struct *vma, unsigned long shift)
> * process cleanup to remove whatever mess we made.
> */
> if (length != move_page_tables(vma, old_start,
> - vma, new_start, length, false))
> + vma, new_start, length, false, true))
> return -ENOMEM;
>
> lru_add_drain();
> diff --git a/include/linux/mm.h b/include/linux/mm.h
> index 406ab9ea818f..e635d1fc73b6 100644
> --- a/include/linux/mm.h
> +++ b/include/linux/mm.h
> @@ -2458,7 +2458,7 @@ int get_cmdline(struct task_struct *task, char *buffer, int buflen);
> extern unsigned long move_page_tables(struct vm_area_struct *vma,
> unsigned long old_addr, struct vm_area_struct *new_vma,
> unsigned long new_addr, unsigned long len,
> - bool need_rmap_locks);
> + bool need_rmap_locks, bool for_stack);
>
> /*
> * Flags used by change_protection(). For now we make it a bitmap so
> diff --git a/mm/mremap.c b/mm/mremap.c
> index 1011326b7b80..2b51f8b7cad8 100644
> --- a/mm/mremap.c
> +++ b/mm/mremap.c
> @@ -490,12 +490,13 @@ static bool move_pgt_entry(enum pgt_entry entry, struct vm_area_struct *vma,
> }
>
> /*
> - * A helper to check if a previous mapping exists. Required for
> - * move_page_tables() and realign_addr() to determine if a previous mapping
> - * exists before we can do realignment optimizations.
> + * A helper to check if aligning down is OK. The aligned address should fall
> + * on *no mapping*. For the stack moving down, that's a special move within
> + * the VMA that is created to span the source and destination of the move,
> + * so we make an exception for it.
> */
> static bool can_align_down(struct vm_area_struct *vma, unsigned long addr_to_align,
> - unsigned long mask)
> + unsigned long mask, bool for_stack)
> {
> unsigned long addr_masked = addr_to_align & mask;
>
> @@ -504,9 +505,13 @@ static bool can_align_down(struct vm_area_struct *vma, unsigned long addr_to_ali
> * of the corresponding VMA, we can't align down or we will destroy part
> * of the current mapping.
> */
> - if (vma->vm_start != addr_to_align)
> + if (!for_stack && vma->vm_start != addr_to_align)
> return false;
>
> + /* In the stack case we explicitly permit in-VMA alignment. */
> + if (for_stack && addr_masked >= vma->vm_start)
> + return true;
> +
> /*
> * Make sure the realignment doesn't cause the address to fall on an
> * existing mapping.
> @@ -517,7 +522,7 @@ static bool can_align_down(struct vm_area_struct *vma, unsigned long addr_to_ali
> /* Opportunistically realign to specified boundary for faster copy. */
> static void try_realign_addr(unsigned long *old_addr, struct vm_area_struct *old_vma,
> unsigned long *new_addr, struct vm_area_struct *new_vma,
> - unsigned long mask)
> + unsigned long mask, bool for_stack)
> {
> /* Skip if the addresses are already aligned. */
> if ((*old_addr & ~mask) == 0)
> @@ -528,8 +533,8 @@ static void try_realign_addr(unsigned long *old_addr, struct vm_area_struct *old
> return;
>
> /* Ensure realignment doesn't cause overlap with existing mappings. */
> - if (!can_align_down(old_vma, *old_addr, mask) ||
> - !can_align_down(new_vma, *new_addr, mask))
> + if (!can_align_down(old_vma, *old_addr, mask, for_stack) ||
> + !can_align_down(new_vma, *new_addr, mask, for_stack))
> return;
>
> *old_addr = *old_addr & mask;
> @@ -539,7 +544,7 @@ static void try_realign_addr(unsigned long *old_addr, struct vm_area_struct *old
> unsigned long move_page_tables(struct vm_area_struct *vma,
> unsigned long old_addr, struct vm_area_struct *new_vma,
> unsigned long new_addr, unsigned long len,
> - bool need_rmap_locks)
> + bool need_rmap_locks, bool for_stack)
> {
> unsigned long extent, old_end;
> struct mmu_notifier_range range;
> @@ -559,9 +564,9 @@ unsigned long move_page_tables(struct vm_area_struct *vma,
> * If possible, realign addresses to PMD boundary for faster copy.
> * Only realign if the mremap copying hits a PMD boundary.
> */
> - if ((vma != new_vma)
> - && (len >= PMD_SIZE - (old_addr & ~PMD_MASK)))
> - try_realign_addr(&old_addr, vma, &new_addr, new_vma, PMD_MASK);
> + if (len >= PMD_SIZE - (old_addr & ~PMD_MASK))
> + try_realign_addr(&old_addr, vma, &new_addr, new_vma, PMD_MASK,
> + for_stack);
>
> flush_cache_range(vma, old_addr, old_end);
> mmu_notifier_range_init(&range, MMU_NOTIFY_UNMAP, 0, vma->vm_mm,
> @@ -708,7 +713,7 @@ static unsigned long move_vma(struct vm_area_struct *vma,
> }
>
> moved_len = move_page_tables(vma, old_addr, new_vma, new_addr, old_len,
> - need_rmap_locks);
> + need_rmap_locks, false);
> if (moved_len < old_len) {
> err = -ENOMEM;
> } else if (vma->vm_ops && vma->vm_ops->mremap) {
> @@ -722,7 +727,7 @@ static unsigned long move_vma(struct vm_area_struct *vma,
> * and then proceed to unmap new area instead of old.
> */
> move_page_tables(new_vma, new_addr, vma, old_addr, moved_len,
> - true);
> + true, false);
> vma = new_vma;
> old_len = new_len;
> old_addr = new_addr;
> --
> 2.42.0.283.g2d96d420d3-goog
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2023-09-08 13:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-03 15:13 [PATCH v6 0/7] Optimize mremap during mutual alignment within PMD Joel Fernandes (Google)
2023-09-03 15:13 ` [PATCH v6 1/7] mm/mremap: Optimize the start addresses in move_page_tables() Joel Fernandes (Google)
2023-09-08 13:07 ` Michal Hocko
2023-09-08 13:26 ` Joel Fernandes
2023-09-03 15:13 ` [PATCH v6 2/7] mm/mremap: Allow moves within the same VMA for stack moves Joel Fernandes (Google)
2023-09-05 6:47 ` Lorenzo Stoakes
2023-09-08 13:11 ` Michal Hocko [this message]
2023-09-03 15:13 ` [PATCH v6 3/7] selftests: mm: Fix failure case when new remap region was not found Joel Fernandes (Google)
2023-09-03 15:13 ` [PATCH v6 4/7] selftests: mm: Add a test for mutually aligned moves > PMD size Joel Fernandes (Google)
2023-09-03 15:13 ` [PATCH v6 5/7] selftests: mm: Add a test for remapping to area immediately after existing mapping Joel Fernandes (Google)
2023-09-03 15:13 ` [PATCH v6 6/7] selftests: mm: Add a test for remapping within a range Joel Fernandes (Google)
2023-09-05 6:48 ` Lorenzo Stoakes
2023-09-03 15:13 ` [PATCH v6 7/7] selftests: mm: Add a test for moving from an offset from start of mapping Joel Fernandes (Google)
2023-09-18 15:35 ` [PATCH v6 0/7] Optimize mremap during mutual alignment within PMD zhenyu zhang
2023-09-19 12:31 ` zhenyu 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=ZPsdbUM9J3LPVDfq@dhcp22.suse.cz \
--to=mhocko@suse.com \
--cc=joel@joelfernandes.org \
--cc=kaleshsingh@google.com \
--cc=kirill@shutemov.name \
--cc=liam.howlett@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lokeshgidra@google.com \
--cc=lstoakes@gmail.com \
--cc=paulmck@kernel.org \
--cc=shuah@kernel.org \
--cc=surenb@google.com \
--cc=torvalds@linux-foundation.org \
--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