From: Heiko Carstens <hca@linux.ibm.com>
To: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Jeff Xu <jeffxu@chromium.org>,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
"Liam R . Howlett" <Liam.Howlett@oracle.com>,
Kees Cook <kees@kernel.org>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Sven Schnelle <svens@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-hardening@vger.kernel.org
Subject: Re: [PATCH mm-unstable 1/2] mseal sysmap: generic vdso vvar mapping
Date: Tue, 11 Mar 2025 14:32:58 +0100 [thread overview]
Message-ID: <20250311133258.12846C3b-hca@linux.ibm.com> (raw)
In-Reply-To: <20250311135542-574f3a8a-525f-4e84-9f04-c9d1ded0deef@linutronix.de>
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@canb.auug.org.au/
> https://lore.kernel.org/lkml/20250311150847.5a63db36@canb.auug.org.au/
Yes, but Andrew added your patches into his tree and on top of that
the mseal patches:
https://lore.kernel.org/all/20250306235802.ff0f406acd0117bcfe927082@linux-foundation.org/
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.
next prev parent reply other threads:[~2025-03-11 13:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-11 12:33 [PATCH mm-unstable 0/2] mseal system mappings fix + s390 enablement Heiko Carstens
2025-03-11 12:33 ` [PATCH mm-unstable 1/2] mseal sysmap: generic vdso vvar mapping Heiko Carstens
2025-03-11 12:59 ` Thomas Weißschuh
2025-03-11 13:32 ` Heiko Carstens [this message]
2025-03-11 14:36 ` Lorenzo Stoakes
2025-03-11 21:54 ` Jeff Xu
2025-03-11 12:33 ` [PATCH mm-unstable 2/2] mseal sysmap: enable s390 Heiko Carstens
2025-03-11 14:37 ` Lorenzo Stoakes
2025-03-11 21:55 ` Jeff Xu
2025-03-11 22:12 ` Jeff Xu
2025-03-12 15:39 ` Heiko Carstens
2025-03-12 23:53 ` Jeff Xu
2025-03-11 13:02 ` [PATCH mm-unstable 0/2] mseal system mappings fix + s390 enablement Lorenzo Stoakes
2025-03-11 13:37 ` Heiko Carstens
2025-03-11 13:42 ` Lorenzo Stoakes
2025-03-11 14:06 ` Heiko Carstens
2025-03-11 14:09 ` Lorenzo Stoakes
2025-03-11 14:21 ` Heiko Carstens
2025-03-11 14:30 ` Lorenzo Stoakes
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=20250311133258.12846C3b-hca@linux.ibm.com \
--to=hca@linux.ibm.com \
--cc=Liam.Howlett@oracle.com \
--cc=agordeev@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=borntraeger@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=jeffxu@chromium.org \
--cc=kees@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=svens@linux.ibm.com \
--cc=thomas.weissschuh@linutronix.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox