From: Blazej Kucman <blazej.kucman@intel.com>
To: mariusz.tkaczyk@linux.intel.com, jes@trained-monkey.org
Cc: linux-raid@vger.kernel.org
Subject: [PATCH 0/5] Disk encryption status handling
Date: Mon, 18 Mar 2024 17:25:30 +0100 [thread overview]
Message-ID: <20240318162535.13674-1-blazej.kucman@intel.com> (raw)
The purpose of this series is to add functionality of
reading information about the encryption status of
OPAL NVMe/SATA and SATA drives and use this
information for purposes of IMSM metadata,
which introduces restrictions on the possibility of mixing disks
with encryption enabled and disabled because of security reasons.
Blazej Kucman (5):
Add reading Opal NVMe encryption information
Add reading SATA encryption information
Add key ENCRYPTION_NO_VERIFY to conf
imsm: print disk encryption information
imsm: drive encryption policy implementation
Makefile | 4 +-
config.c | 25 +-
drive_encryption.c | 724 +++++++++++++++++++++++++++++++++++++++++++++
drive_encryption.h | 37 +++
mdadm.conf.5.in | 16 +
mdadm.h | 4 +
super-intel.c | 117 +++++++-
sysfs.c | 29 ++
8 files changed, 947 insertions(+), 9 deletions(-)
create mode 100644 drive_encryption.c
create mode 100644 drive_encryption.h
--
2.35.3
next reply other threads:[~2024-03-18 16:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-18 16:25 Blazej Kucman [this message]
2024-03-18 16:25 ` [PATCH 1/5] Add reading Opal NVMe encryption information Blazej Kucman
2024-03-18 17:56 ` Paul Menzel
2024-03-22 11:55 ` Blazej Kucman
2024-03-18 16:25 ` [PATCH 2/5] Add reading SATA " Blazej Kucman
2024-03-18 16:25 ` [PATCH 3/5] Add key ENCRYPTION_NO_VERIFY to conf Blazej Kucman
2024-03-18 18:00 ` Paul Menzel
2024-03-18 16:25 ` [PATCH 4/5] imsm: print disk encryption information Blazej Kucman
2024-03-18 16:25 ` [PATCH 5/5] imsm: drive encryption policy implementation Blazej Kucman
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=20240318162535.13674-1-blazej.kucman@intel.com \
--to=blazej.kucman@intel.com \
--cc=jes@trained-monkey.org \
--cc=linux-raid@vger.kernel.org \
--cc=mariusz.tkaczyk@linux.intel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).