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

[Andrew Morton]

On Wed, 1 Jul 2026 13:01:15 +0800 Vivian Wang <wangruikang@xxxxxxxxxxx> wrote:

> On 7/1/26 12:11, Andrew Morton wrote:
> > [...]
> >
> > btw, AI review suggests that there's a missing barrier in there (a
> > pre-existing thing)
> >
> > 	https://sashiko.dev/#/patchset/20260630-mark-after-vmemmap-populate-v4-1-febbc15da028@xxxxxxxxxxx
> 
> Interestingly, whatever thingy that is sending patches into AI review
> seems to completely strip the message below the "---",

Hey, what do you expect for $2,000,000,000,000?

> 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've reported "being able to read below the cut" as a feature request to
> Sashiko: https://github.com/sashiko-dev/sashiko/issues/306

I'm not sure that Sashiko would grok (heh) this if it was above the
cut.