From: Linus Walleij <linus.walleij@linaro.org>
To: Shyam Saini <shyamsaini@linux.microsoft.com>
Cc: "Sumit Garg" <sumit.garg@linaro.org>,
"Ilias Apalodimas" <ilias.apalodimas@linaro.org>,
"Jens Wiklander" <jens.wiklander@linaro.org>,
"Jerome Forissier" <jerome.forissier@linaro.org>,
"Ulf Hansson" <ulf.hansson@linaro.org>,
linux-kernel@vger.kernel.org, linux-mmc@vger.kernel.org,
op-tee@lists.trustedfirmware.org, linux-scsi@vger.kernel.org,
"Alex Bennée" <alex.bennee@linaro.org>,
"Tomas Winkler" <tomas.winkler@intel.com>,
"Arnd Bergmann" <arnd.bergmann@linaro.org>,
"Tyler Hicks" <code@tyhicks.com>,
"Srivatsa S . Bhat" <srivatsa@csail.mit.edu>,
"Paul Moore" <paul@paul-moore.com>,
"Allen Pais" <apais@linux.microsoft.com>
Subject: Re: [RFC, PATCH 1/1] rpmb: add Replay Protected Memory Block (RPMB) driver
Date: Wed, 23 Aug 2023 10:04:20 +0200 [thread overview]
Message-ID: <CACRpkdb=AnJXG2J_DRsN-RUEh=7_eAs8+_CxPYuueVM0c=DP3Q@mail.gmail.com> (raw)
In-Reply-To: <226aa02d-1247-a42c-123d-1c86b6b43d9f@linux.microsoft.com>
On Tue, Aug 22, 2023 at 9:07 PM Shyam Saini
<shyamsaini@linux.microsoft.com> wrote:
> do we plan to disable access to RPMB devices, once we have this RPMB
> driver in place. User space tools like mmc-utils/nvme/ufs utils
> can still access RPMB and programme the key and should
> RPMB driver deny access to RPMB ?
We don't break userspace. Just not. This is not an option.
The RPMB subsystem simply has to provide the rpmb character
device the same way the MMC subsystem did, or provide an
in-kernel backend to the MMC subsystem so that it can provide
the same device. Whatever solution is best.
No deprecation and deletion and breaking userspace. Ever.
Yours,
Linus Walleij
next prev parent reply other threads:[~2023-08-23 8:06 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-22 1:40 [RFC, PATCH 0/1] Replay Protected Memory Block (RPMB) driver Shyam Saini
2023-07-22 1:40 ` [RFC, PATCH 1/1] rpmb: add " Shyam Saini
2023-07-22 3:11 ` Randy Dunlap
2023-07-26 20:10 ` Shyam Saini
2023-08-07 15:00 ` Ulf Hansson
2023-08-16 23:31 ` Shyam Saini
2023-08-21 9:49 ` Jerome Forissier
2023-08-21 10:03 ` Sumit Garg
2023-08-21 11:18 ` Jens Wiklander
2023-08-21 11:54 ` Sumit Garg
2023-08-21 11:55 ` Ilias Apalodimas
2023-08-21 12:17 ` Sumit Garg
2023-08-22 19:07 ` Shyam Saini
2023-08-23 8:04 ` Linus Walleij [this message]
2023-08-24 14:07 ` Sumit Garg
2023-08-21 12:35 ` Jerome Forissier
2023-08-22 18:59 ` Shyam Saini
2023-08-24 14:01 ` Sumit Garg
2023-08-22 18:47 ` Shyam Saini
2023-08-07 21:02 ` Bart Van Assche
2023-08-22 18:43 ` Shyam Saini
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='CACRpkdb=AnJXG2J_DRsN-RUEh=7_eAs8+_CxPYuueVM0c=DP3Q@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=apais@linux.microsoft.com \
--cc=arnd.bergmann@linaro.org \
--cc=code@tyhicks.com \
--cc=ilias.apalodimas@linaro.org \
--cc=jens.wiklander@linaro.org \
--cc=jerome.forissier@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=op-tee@lists.trustedfirmware.org \
--cc=paul@paul-moore.com \
--cc=shyamsaini@linux.microsoft.com \
--cc=srivatsa@csail.mit.edu \
--cc=sumit.garg@linaro.org \
--cc=tomas.winkler@intel.com \
--cc=ulf.hansson@linaro.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;
as well as URLs for NNTP newsgroup(s).