Re: [PATCH mm-unstable 0/2] mseal system mappings fix + s390 enablement

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Mar 11, 2025 at 01:33:24PM +0100, Heiko Carstens wrote:
> When rebasing the mseal series on top of the generic vdso data storage
> the VM_SEALED_SYSMAP vm flag for the vvar mapping got lost. Add that again.

I'm confused by this? Some merge patch resolution thing?

I don't think this should be at the top of a description of a series, seems more
like an addendum.

>
> Also add s390 support for MSEAL_SYSTEM_MAPPINGS.

'Also' = the whole thing this series does?

Can you confirm that s390 absolutely does not rely upon
moving/manipulating/etc. the VDSO, VVAR, etc. mappings?

You should say that here.

>
> Heiko Carstens (2):
>   mseal sysmap: generic vdso vvar mapping
>   mseal sysmap: enable s390
>
>  arch/s390/Kconfig       | 1 +
>  arch/s390/kernel/vdso.c | 2 +-
>  lib/vdso/datastore.c    | 3 ++-
>  3 files changed, 4 insertions(+), 2 deletions(-)
>
> --
> 2.45.2
>




[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux