lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 4 Jul 2022 16:34:04 +0200 From: Greg KH <gregkh@...uxfoundation.org> To: Martin Fernandez <martin.fernandez@...ypsium.com> Cc: linux-kernel@...r.kernel.org, linux-efi@...r.kernel.org, platform-driver-x86@...r.kernel.org, linux-mm@...ck.org, kunit-dev@...glegroups.com, linux-kselftest@...r.kernel.org, tglx@...utronix.de, mingo@...hat.com, bp@...en8.de, dave.hansen@...ux.intel.com, x86@...nel.org, hpa@...or.com, ardb@...nel.org, dvhart@...radead.org, andy@...radead.org, rafael@...nel.org, rppt@...nel.org, akpm@...ux-foundation.org, daniel.gutson@...ypsium.com, hughsient@...il.com, alex.bazhaniuk@...ypsium.com, alison.schofield@...el.com, keescook@...omium.org Subject: Re: [PATCH v9 9/9] drivers/node: Show in sysfs node's crypto capabilities On Mon, Jul 04, 2022 at 10:58:33AM -0300, Martin Fernandez wrote: > Show in each node in sysfs if its memory is able to do be encrypted by > the CPU; on EFI systems: if all its memory is marked with > EFI_MEMORY_CPU_CRYPTO in the EFI memory map. > > Signed-off-by: Martin Fernandez <martin.fernandez@...ypsium.com> > --- > Documentation/ABI/testing/sysfs-devices-node | 10 ++++++++++ > drivers/base/node.c | 10 ++++++++++ > 2 files changed, 20 insertions(+) > create mode 100644 Documentation/ABI/testing/sysfs-devices-node > > diff --git a/Documentation/ABI/testing/sysfs-devices-node b/Documentation/ABI/testing/sysfs-devices-node > new file mode 100644 > index 000000000000..0e95420bd7c5 > --- /dev/null > +++ b/Documentation/ABI/testing/sysfs-devices-node > @@ -0,0 +1,10 @@ > +What: /sys/devices/system/node/nodeX/crypto_capable > +Date: April 2022 > +Contact: Martin Fernandez <martin.fernandez@...ypsium.com> > +Users: fwupd (https://fwupd.org) > +Description: > + This value is 1 if all system memory in this node is > + capable of being protected with the CPU's memory > + cryptographic capabilities. It is 0 otherwise. > + On EFI systems the node will be marked with > + EFI_MEMORY_CPU_CRYPTO. Where will such a node be "marked"? I do not understand this last sentence, sorry, can you please reword this? And why is EFI an issue here at all? thanks, greg k-h
Powered by blists - more mailing lists