From: Jens Axboe <axboe@kernel.dk>
To: Luca Boccassi <bluca@debian.org>, linux-block@vger.kernel.org
Cc: Milan Broz <gmazyland@gmail.com>
Subject: Re: [PATCH v7] block: sed-opal: Add ioctl to return device status
Date: Fri, 19 Aug 2022 10:53:42 -0600 [thread overview]
Message-ID: <36444e6a-c766-051c-011d-2e28b63ac714@kernel.dk> (raw)
In-Reply-To: <CAMw=ZnRSV3uF+HFjvL5Fdb_S_RB=3YrWT4ZqtG9e4ZmJTpehVQ@mail.gmail.com>
On 8/19/22 4:45 AM, Luca Boccassi wrote:
> On Tue, 16 Aug 2022 at 15:07, <luca.boccassi@gmail.com> wrote:
>>
>> From: "dougmill@linux.vnet.ibm.com" <dougmill@linux.vnet.ibm.com>
>>
>> Provide a mechanism to retrieve basic status information about
>> the device, including the "supported" flag indicating whether
>> SED-OPAL is supported. The information returned is from the various
>> feature descriptors received during the discovery0 step, and so
>> this ioctl does nothing more than perform the discovery0 step
>> and then save the information received. See "struct opal_status"
>> and OPAL_FL_* bits for the status information currently returned.
>>
>> This is necessary to be able to check whether a device is OPAL
>> enabled, set up, locked or unlocked from userspace programs
>> like systemd-cryptsetup and libcryptsetup. Right now we just
>> have to assume the user 'knows' or blindly attempt setup/lock/unlock
>> operations.
>>
>> Signed-off-by: Douglas Miller <dougmill@linux.vnet.ibm.com>
>> Tested-by: Luca Boccassi <bluca@debian.org>
>> Reviewed-by: Scott Bauer <sbauer@plzdonthack.me>
>> Acked-by: Christian Brauner (Microsoft) <brauner@kernel.org>
>> ---
>> v2: https://patchwork.kernel.org/project/linux-block/patch/612795b5.tj7FMS9wzchsMzrK%25dougmill@linux.vnet.ibm.com/
>> v3: resend on request, after rebasing and testing on my machine
>> https://patchwork.kernel.org/project/linux-block/patch/20220125215248.6489-1-luca.boccassi@gmail.com/
>> v4: it's been more than 7 months and no alternative approach has appeared.
>> we really need to be able to identify and query the status of a sed-opal
>> device, so rebased and resending.
>> v5: as requested by reviewer, add __32 reserved to the UAPI ioctl struct to align to 64
>> bits and to reserve space for future expansion
>> v6: as requested by reviewer, update commit message with use case
>> v7: as requested by reviewer, remove braces around single-line 'if'
>> added received acked-by/reviewed-by tags
>>
>> block/opal_proto.h | 5 ++
>> block/sed-opal.c | 89 ++++++++++++++++++++++++++++++-----
>> include/linux/sed-opal.h | 1 +
>> include/uapi/linux/sed-opal.h | 13 +++++
>> 4 files changed, 96 insertions(+), 12 deletions(-)
>
> Hello Jens,
>
> Is there anything else I can do for this patch? I've got two acks. We
> really need this interface in place to start working on supporting
> sed/opal in cryptsetup.
It's just bad timing, since we just left the merge window. I'll queue it
up when I open up the block bits for 6.1.
--
Jens Axboe
next prev parent reply other threads:[~2022-08-19 17:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-16 14:07 [PATCH v7] block: sed-opal: Add ioctl to return device status luca.boccassi
2022-08-19 10:45 ` Luca Boccassi
2022-08-19 16:53 ` Jens Axboe [this message]
2022-08-19 17:00 ` Luca Boccassi
2022-08-19 20:56 ` Jens Axboe
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=36444e6a-c766-051c-011d-2e28b63ac714@kernel.dk \
--to=axboe@kernel.dk \
--cc=bluca@debian.org \
--cc=gmazyland@gmail.com \
--cc=linux-block@vger.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