From: Liam Howlett <liam.howlett@oracle.com>
To: "maple-tree@lists.infradead.org" <maple-tree@lists.infradead.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Hugh Dickins <hughd@google.com>
Subject: Re: [PATCH] mm/mmap: Fix locking issues in vma_expand()
Date: Tue, 12 Jul 2022 14:48:39 +0000 [thread overview]
Message-ID: <20220712144831.7nmppo5p5jd2k34b@revolver> (raw)
In-Reply-To: <20220712144112.4189027-1-Liam.Howlett@oracle.com>
Please disregard this patch, it is missing 1/2 the fix and the fixes tag
in the log message. The proper fix will be arriving shortly.
Sorry about the noise.
* Liam R. Howlett <Liam.Howlett@oracle.com> [220712 10:41]:
> Hugh noted that the locking was mixed up in vma_expand(), revert to the
> correct order.
>
> Suggested-by: Hugh Dickins <hughd@google.com>
> Signed-off-by: Liam R. Howlett <Liam.Howlett@oracle.com>
> ---
> mm/mmap.c | 14 +++++++++-----
> 1 file changed, 9 insertions(+), 5 deletions(-)
>
> diff --git a/mm/mmap.c b/mm/mmap.c
> index 9eb663cde5c7..001b54fe19b4 100644
> --- a/mm/mmap.c
> +++ b/mm/mmap.c
> @@ -574,7 +574,8 @@ inline int vma_expand(struct ma_state *mas, struct vm_area_struct *vma,
> if (next->anon_vma && !vma->anon_vma) {
> int error;
>
> - vma->anon_vma = next->anon_vma;
> + anon_vma = next->anon_vma;
> + vma->anon_vma = anon_vma;
> error = anon_vma_clone(vma, next);
> if (error)
> return error;
> @@ -592,16 +593,19 @@ inline int vma_expand(struct ma_state *mas, struct vm_area_struct *vma,
>
> vma_adjust_trans_huge(vma, start, end, 0);
>
> + if (file) {
> + mapping = file->f_mapping;
> + root = &mapping->i_mmap;
> + uprobe_munmap(vma, vma->vm_start, vma->vm_end);
> + i_mmap_lock_write(mapping);
> + }
> +
> if (anon_vma) {
> anon_vma_lock_write(anon_vma);
> anon_vma_interval_tree_pre_update_vma(vma);
> }
>
> if (file) {
> - mapping = file->f_mapping;
> - root = &mapping->i_mmap;
> - uprobe_munmap(vma, vma->vm_start, vma->vm_end);
> - i_mmap_lock_write(mapping);
> flush_dcache_mmap_lock(mapping);
> vma_interval_tree_remove(vma, root);
> }
> --
> 2.35.1
next prev parent reply other threads:[~2022-07-12 14:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-12 14:41 Liam Howlett
2022-07-12 14:48 ` Liam Howlett [this message]
2022-07-12 14:49 Liam Howlett
2022-07-15 18:49 ` Liam Howlett
2022-07-15 23:16 ` Andrew Morton
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=20220712144831.7nmppo5p5jd2k34b@revolver \
--to=liam.howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=maple-tree@lists.infradead.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