All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brad Hawthorne <brad@sim.vu>
To: thehajime@gmail.com
Cc: Brad Hawthorne <brad@sim.vu>, Lorenzo Stoakes <ljs@kernel.org>,
	"Liam R. Howlett" <liam@infradead.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-mm@kvack.org
Subject: Re: [RFC PATCH 1/6] mm: nommu: fix do_mremap() to correctly update internal states
Date: Fri, 20 Nov 2026 16:10:00 -0600	[thread overview]
Message-ID: <20261120221021.789792-1-brad@sim.vu> (raw)
In-Reply-To: <m21pc0qquc.wl-thehajime@gmail.com>

Hi Hajime,

I hit the do_mremap() stale range on an Adafruit Fruit Jam board
(RP2350, Cortex-M33) running 7.3.1; the code is unchanged in 7.3.4
and in 7.3.5, the current stable release. I reproduced its
consequence under QEMU mps2-an385 on today's mm-unstable: an
unprivileged mmap() of 8 pages, mremap() to 4, munmap() and exit
gives SLUB "Object already free" from exit_mmap(). On the board the
next exec then faults the kernel; with the patch applied to the same
kernel it runs on (11 of 11 runs).

Following Lorenzo's request for a minimal fix-only patch, I have one
that only keeps the maple tree in step: it clears the given-up range on
a shrink and stores the VMA over its new extent on a grow, with
Fixes: 524e00b36e8c and Cc: stable. It leaves the i_mmap tree, the
region's pages and the rest of your series alone.

I don't want to step on your rework. Would you rather carry it in your
series, or shall I send it as a separate patch with you on Cc? Either
is fine by me, and I'm glad to test whatever you post on the board.

Thanks,
Brad


  reply	other threads:[~2026-11-20 22:11 UTC|newest]

Thread overview: 46+ 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-11-20 22:10       ` Brad Hawthorne [this message]
2026-11-21  6:53         ` 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)
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=20261120221021.789792-1-brad@sim.vu \
    --to=brad@sim.vu \
    --cc=akpm@linux-foundation.org \
    --cc=liam@infradead.org \
    --cc=linux-mm@kvack.org \
    --cc=ljs@kernel.org \
    --cc=thehajime@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.