Re: [PATCH mm-unstable 1/2] mseal sysmap: generic vdso vvar mapping

[Heiko Carstens]

On Tue, Mar 11, 2025 at 01:59:21PM +0100, Thomas Weißschuh wrote:
> Hi Heiko,
> 
> On Tue, Mar 11, 2025 at 01:33:25PM +0100, Heiko Carstens wrote:
> > With the introduction of the generic vdso data storage the VM_SEALED_SYSMAP
> > vm flag must be moved from the architecture specific
> > _install_special_mapping() call [1] [2] which maps the vvar mapping to
> > generic code.
> 
> I think this change should be part of the merge commit between the
> trees carrying the generic vdso data storage and mseal for system mappings.
> 
> https://lore.kernel.org/lkml/20250307151426.5f3c0c39@xxxxxxxxxxxxxxxx/
> https://lore.kernel.org/lkml/20250311150847.5a63db36@xxxxxxxxxxxxxxxx/

Yes, but Andrew added your patches into his tree and on top of that
the mseal patches:
https://lore.kernel.org/all/20250306235802.ff0f406acd0117bcfe927082@xxxxxxxxxxxxxxxxxxxx/
https://web.git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git/log/?h=mm-unstable

When doing that the vvar bits got lost. I don't know what Andrew's
plans for the merge window are, but right now there is no merge commit
which could be fixed.