Re: [PATCH v4] riscv: mm: Avoid spurious fault after hotplugging vmemmap

[Andrew Morton]

On Thu, 9 Jul 2026 20:00:08 -0600 (MDT) Paul Walmsley <pjw@xxxxxxxxxx> wrote:

> Hi Andrew,
> 
> On Tue, 30 Jun 2026, Andrew Morton wrote:
> 
> > On Wed, 1 Jul 2026 13:01:15 +0800 Vivian Wang <wangruikang@xxxxxxxxxxx> wrote:
> > 
> > > which made it miss:
> > > 
> > >     Changes in v4:
> > >     - Rebase on v7.2-rc1, drop dependencies
> > >     - (No code changes otherwise)
> > >     - (A concurrency fix for mark_new_valid_map was sent independently)
> > >       https://lore.kernel.org/linux-riscv/20260629-riscv-mm-new-valid-map-ordering-v1-1-60d8c10c6292@xxxxxxxxxxx/
> > >       ^--- this
> > 
> > Cool, I grabbed that.  Same caveats: riscv maintainers, please?
> 
> I just responded to Vivian's v5.  I guess he'll probably do a v6, at which 
> point, will plan to queue it for v7.2-rc here, unless you have any 
> objections?

Go for it, thanks.

When I see a version of this pop up in linux-next I'll drop the mm.git
copy.  This is my standard procedure.