From: Steffen Eiden <seiden@linux.ibm.com>
To: linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org
Cc: Ingo Franzki <ifranzki@linux.ibm.com>,
Harald Freudenberger <freude@linux.ibm.com>,
Christoph Schlameuss <schlameuss@linux.ibm.com>,
Janosch Frank <frankja@linux.ibm.com>,
Claudio Imbrenda <imbrenda@linux.ibm.com>
Subject: [PATCH v3 0/2] s390/uv: Provide host-key hashes in sysfs
Date: Tue, 15 Oct 2024 13:39:38 +0200 [thread overview]
Message-ID: <20241015113940.3088249-1-seiden@linux.ibm.com> (raw)
List the installed host-keys in the sysfs if the machine supports the
Query Ultravisor Keys UVC.
As of now, two types of host-keys are available:
The used/primary host key, and the backup host-key both hastes are
available in a sysfs file.
For forwards compatibility an `all` file is also available that displays
the whole payload (15*32 bytes) and therefore future key hashes.
Sice v2:
* add rb from Janosch (& fix nits)
* slightly refactor sysfs directory creation (Heiko)
Since v1:
* add r-b's from Janoch & Christoph
* fix minor issues (Janosch)
* remove an unnecessary UVC availability-check in uv_query_keys
-> remove Christoph's r-b from patch 2
Steffen Eiden (2):
s390/uv: Refactor uv-sysfs creation
s390/uv: Provide host-key hashes in sysfs
arch/s390/include/asm/uv.h | 17 ++++++
arch/s390/kernel/uv.c | 103 +++++++++++++++++++++++++++++++++----
2 files changed, 110 insertions(+), 10 deletions(-)
--
2.43.0
next reply other threads:[~2024-10-15 11:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-15 11:39 Steffen Eiden [this message]
2024-10-15 11:39 ` [PATCH v3 1/2] s390/uv: Refactor uv-sysfs creation Steffen Eiden
2024-10-15 11:39 ` [PATCH v3 2/2] s390/uv: Provide host-key hashes in sysfs Steffen Eiden
2024-10-23 7:55 ` Steffen Eiden
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=20241015113940.3088249-1-seiden@linux.ibm.com \
--to=seiden@linux.ibm.com \
--cc=frankja@linux.ibm.com \
--cc=freude@linux.ibm.com \
--cc=ifranzki@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=schlameuss@linux.ibm.com \
/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