From: "Roy, Patrick" <roypat@amazon.co.uk>
To: "peterz@infradead.org" <peterz@infradead.org>
Cc: "da.gomez@samsung.com" <da.gomez@samsung.com>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"hch@infradead.org" <hch@infradead.org>,
"hpa@zytor.com" <hpa@zytor.com>,
"linux-kbuild@vger.kernel.org" <linux-kbuild@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-modules@vger.kernel.org" <linux-modules@vger.kernel.org>,
"masahiroy@kernel.org" <masahiroy@kernel.org>,
"mcgrof@kernel.org" <mcgrof@kernel.org>,
"nathan@kernel.org" <nathan@kernel.org>,
"nicolas@fjasle.eu" <nicolas@fjasle.eu>,
"petr.pavlu@suse.com" <petr.pavlu@suse.com>,
"samitolvanen@google.com" <samitolvanen@google.com>,
"x86@kernel.org" <x86@kernel.org>
Subject: RE: [PATCH -v2 0/7] module: Strict per-modname namespaces
Date: Fri, 2 May 2025 11:55:54 +0000 [thread overview]
Message-ID: <20250502115553.27803-1-roypat@amazon.co.uk> (raw)
In-Reply-To: <20241202145946.108093528@infradead.org>
Hi Peter,
Are you still working on this patch series? I'm working on having KVM remove
virtual machine memory from the kernel's direct map, to harden again
speculative execution attacks [1]. At David H.'s LSF/MM/BPF task on
guest_memfd, it was suggested to use per-modname namespaces to export
set_direct_map_valid() specifically for use in KVM to achieve this.
Is there anything I can do to help get this across the finish line
(testing/etc.)?
Best,
Patrick
[1]: https://lore.kernel.org/kvm/20250221160728.1584559-1-roypat@amazon.co.uk/
next prev parent reply other threads:[~2025-05-02 11:56 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-02 14:59 [PATCH -v2 0/7] module: Strict per-modname namespaces Peter Zijlstra
2024-12-02 14:59 ` [PATCH -v2 1/7] module: Convert symbol namespace to string literal Peter Zijlstra
2024-12-02 15:15 ` Peter Zijlstra
2024-12-02 15:22 ` Greg KH
2024-12-02 19:33 ` Linus Torvalds
2024-12-03 19:19 ` Mark Brown
2024-12-03 22:06 ` Mark Brown
2024-12-04 1:11 ` Masahiro Yamada
2024-12-02 14:59 ` [PATCH -v2 2/7] module/modpost: Use for() loop Peter Zijlstra
2025-02-07 8:50 ` Masahiro Yamada
2025-02-07 16:38 ` Masahiro Yamada
2024-12-02 14:59 ` [PATCH -v2 3/7] module/modpost: Add basename helper Peter Zijlstra
2025-02-07 17:56 ` Masahiro Yamada
2024-12-02 14:59 ` [PATCH -v2 4/7] module: Add module specific symbol namespace support Peter Zijlstra
2025-02-07 16:22 ` Masahiro Yamada
2024-12-02 14:59 ` [PATCH -v2 5/7] module: Extend the MODULE_ namespace parsing Peter Zijlstra
2025-02-07 8:41 ` Masahiro Yamada
2025-05-02 13:10 ` Peter Zijlstra
2025-02-07 15:45 ` Masahiro Yamada
2025-05-02 13:11 ` Peter Zijlstra
2024-12-02 14:59 ` [PATCH -v2 6/7] module: Account for the build time module name mangling Peter Zijlstra
2024-12-06 18:35 ` Sean Christopherson
2025-05-02 13:15 ` Peter Zijlstra
2024-12-02 14:59 ` [PATCH -v2 7/7] module: Provide EXPORT_SYMBOL_GPL_FOR() helper Peter Zijlstra
2025-02-07 8:09 ` Masahiro Yamada
2024-12-02 17:36 ` [PATCH -v2 0/7] module: Strict per-modname namespaces Andi Kleen
2024-12-16 16:43 ` Petr Pavlu
2025-02-05 10:14 ` Petr Pavlu
2025-02-07 18:04 ` Masahiro Yamada
2025-05-02 11:55 ` Roy, Patrick [this message]
2025-05-02 12:55 ` Peter Zijlstra
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=20250502115553.27803-1-roypat@amazon.co.uk \
--to=roypat@amazon.co.uk \
--cc=da.gomez@samsung.com \
--cc=gregkh@linuxfoundation.org \
--cc=hch@infradead.org \
--cc=hpa@zytor.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=mcgrof@kernel.org \
--cc=nathan@kernel.org \
--cc=nicolas@fjasle.eu \
--cc=peterz@infradead.org \
--cc=petr.pavlu@suse.com \
--cc=samitolvanen@google.com \
--cc=x86@kernel.org \
/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