From: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
To: Hajime Tazaki <thehajime@gmail.com>
Cc: linux-mm@kvack.org, geert@linux-m68k.org, daniel@thingy.jp,
Andrew Morton <akpm@linux-foundation.org>,
"Liam R. Howlett" <liam@infradead.org>,
Vlastimil Babka <vbabka@kernel.org>,
Jann Horn <jannh@google.com>, Pedro Falcato <pfalcato@suse.de>
Subject: Re: [RFC PATCH 2/6] mm: nommu: use vma_is_anonymous() to check if vmas are anonymous
Date: Fri, 14 Aug 2026 12:52:42 +0100 [thread overview]
Message-ID: <an8Bdv54k2B1o1c2@lucifer> (raw)
In-Reply-To: <20260813063401.1786548-3-thehajime@gmail.com>
On Thu, Aug 13, 2026 at 03:33:57PM +0900, Hajime Tazaki wrote:
> Private file mappings (like those from /dev/zero) can have vma->vm_file
> set but remain structurally anonymous since they lack vm_ops. Testing
> vma->vm_file instead of vma_is_anonymous(vma) might cause mremap to
> return a spurious -EINVAL when userspace attempts to shrink these
> mappings.
>
> This commit fixes this issue by using vma_is_anonymous() instead of
> testing vma->vm_file to address the case of /dev/zero.
>
> Cc: Andrew Morton <akpm@linux-foundation.org>
> Cc: "Liam R. Howlett" <liam@infradead.org>
> Cc: Lorenzo Stoakes <ljs@kernel.org>
> Cc: Vlastimil Babka <vbabka@kernel.org>
> Cc: Jann Horn <jannh@google.com>
> Cc: Pedro Falcato <pfalcato@suse.de>
> Cc: linux-mm@kvack.org
> Closes: https://sashiko.dev/#/patchset/20260710054648.924005-1-thehajime%40gmail.com
> Signed-off-by: Hajime Tazaki <thehajime@gmail.com>
As staged in review on 1/6 you need to squash this somehow.
> ---
> mm/nommu.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/mm/nommu.c b/mm/nommu.c
> index 89444ee2aca6..e40990e15831 100644
> --- a/mm/nommu.c
> +++ b/mm/nommu.c
> @@ -1196,7 +1196,7 @@ unsigned long do_mmap(struct file *file,
> add_nommu_region(region);
>
> /* clear anonymous mappings that don't ask for uninitialized data */
> - if (!vma->vm_file &&
> + if (vma_is_anonymous(vma) &&
> (!IS_ENABLED(CONFIG_MMAP_ALLOW_UNINITIALIZED) ||
> !(flags & MAP_UNINITIALIZED)))
> memset((void *)region->vm_start, 0,
> @@ -1328,7 +1328,7 @@ static int split_vma(struct vma_iterator *vmi, struct vm_area_struct *vma,
>
> /* we're only permitted to split anonymous regions (these should have
> * only a single usage on the region) */
> - if (vma->vm_file)
> + if (!vma_is_anonymous(vma))
> return -ENOMEM;
>
> mm = vma->vm_mm;
> @@ -1484,7 +1484,7 @@ int do_munmap(struct mm_struct *mm, unsigned long start, size_t len, struct list
> }
>
> /* we're allowed to split an anonymous VMA but not a file-backed one */
> - if (vma->vm_file) {
> + if (!vma_is_anonymous(vma)) {
> do {
> if (start > vma->vm_start)
> return -EINVAL;
> @@ -1617,7 +1617,7 @@ static unsigned long do_mremap(unsigned long addr,
> /* like do_munmap(), we're allowed to shrink an anonymous VMA but not
> * a file-backed one
> */
> - if (vma->vm_file)
> + if (!vma_is_anonymous(vma))
> return (unsigned long) -EINVAL;
>
> /* vmi_shrink_vma() needs from/to pointers to be removed,
> --
> 2.43.0
>
--
Cheers, Lorenzo
next prev parent reply other threads:[~2026-08-14 11:53 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-13 6:33 [RFC PATCH 0/6] fix nommu mmap and add nommu kselftests Hajime Tazaki
2026-08-13 6:33 ` [RFC PATCH 1/6] mm: nommu: fix do_mremap() to correctly update internal states Hajime Tazaki
2026-08-14 11:52 ` Lorenzo Stoakes (ARM)
2026-08-14 22:28 ` Hajime Tazaki
2026-08-13 6:33 ` [RFC PATCH 2/6] mm: nommu: use vma_is_anonymous() to check if vmas are anonymous Hajime Tazaki
2026-08-14 11:52 ` Lorenzo Stoakes (ARM) [this message]
2026-08-14 22:29 ` Hajime Tazaki
2026-08-13 6:33 ` [RFC PATCH 3/6] mm: nommu: fix an issue on map request to /dev/zero Hajime Tazaki
2026-08-13 12:19 ` Greg Kroah-Hartman
2026-08-13 12:43 ` Daniel Palmer
2026-08-13 13:29 ` Lorenzo Stoakes (ARM)
2026-08-13 13:51 ` Daniel Palmer
2026-08-13 13:58 ` Lorenzo Stoakes (ARM)
2026-08-13 14:06 ` Greg Kroah-Hartman
2026-08-14 12:42 ` Hajime Tazaki
2026-08-14 13:02 ` Lorenzo Stoakes (ARM)
2026-08-17 8:15 ` Hajime Tazaki
2026-08-13 14:02 ` Greg Kroah-Hartman
2026-08-13 14:10 ` Lorenzo Stoakes (ARM)
2026-08-14 9:09 ` Geert Uytterhoeven
2026-08-13 13:22 ` Matthew Wilcox
2026-08-13 13:32 ` Lorenzo Stoakes (ARM)
2026-08-13 13:43 ` Lorenzo Stoakes (ARM)
2026-08-13 14:04 ` Greg Kroah-Hartman
2026-08-14 12:42 ` Hajime Tazaki
2026-08-14 12:37 ` Lorenzo Stoakes (ARM)
2026-08-25 1:57 ` Hajime Tazaki
2026-08-13 6:33 ` [RFC PATCH 4/6] selftests: fix build errors on alpine linux Hajime Tazaki
2026-08-14 9:34 ` Pedro Falcato
2026-08-14 12:44 ` Hajime Tazaki
2026-08-14 12:39 ` Lorenzo Stoakes (ARM)
2026-08-14 22:29 ` Hajime Tazaki
2026-08-13 6:34 ` [RFC PATCH 5/6] selftests: run tests on nommu architecture Hajime Tazaki
2026-08-14 12:50 ` Lorenzo Stoakes (ARM)
2026-08-14 14:34 ` Mark Brown
2026-08-15 21:58 ` Hajime Tazaki
2026-08-15 21:58 ` Hajime Tazaki
2026-08-13 6:34 ` [RFC PATCH 6/6] selftests/mm: add nommu mmap and mremap behavior tests Hajime Tazaki
2026-08-14 13:28 ` Lorenzo Stoakes (ARM)
2026-08-14 22:35 ` Hajime Tazaki
2026-08-14 11:24 ` [RFC PATCH 0/6] fix nommu mmap and add nommu kselftests Lorenzo Stoakes (ARM)
2026-08-14 11:26 ` Lorenzo Stoakes (ARM)
2026-08-14 22:27 ` Hajime Tazaki
2026-08-15 11:53 ` Geert Uytterhoeven
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=an8Bdv54k2B1o1c2@lucifer \
--to=ljs@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=daniel@thingy.jp \
--cc=geert@linux-m68k.org \
--cc=jannh@google.com \
--cc=liam@infradead.org \
--cc=linux-mm@kvack.org \
--cc=pfalcato@suse.de \
--cc=thehajime@gmail.com \
--cc=vbabka@kernel.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