From: Adrian Hunter <adrian.hunter@intel.com>
To: "Christian Löhle" <CLoehle@hyperstone.com>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "ulf.hansson@linaro.org" <ulf.hansson@linaro.org>
Subject: Re: [PATCH] mmc: core: Do not require secure trim for discard
Date: Thu, 17 Nov 2022 10:19:34 +0200 [thread overview]
Message-ID: <bf2c46b3-1117-55dd-ed89-7f4d3ff37b7e@intel.com> (raw)
In-Reply-To: <8a17ed3e0eea4aaa82afd0af3b45bcaf@hyperstone.com>
On 14/11/22 15:26, Christian Löhle wrote:
> Discard feature is independent of security features.
> The support check for all trims and discard falsely checked
> for secure trim/discard, but in the discard case this is not
> mandated by the spec.
>
"Discard" was added after "Trim", so while MMC_TRIM_ARGS made
sense originally, that stopped with:
commit b3bf915308ca ("mmc: core: new discard feature support at eMMC v4.5")
So this could have that as a fixes tag.
Also MMC_TRIM_ARGS is a bit of a misleading name since it covers
one of the bits of MMC_DISCARD_ARG, so I suggest a second patch to
tidy things up.
Perhaps rename it and change the value to 8003 e.g.
#define MMC_TRIM_OR_DISCARD_ARGS 0x00008003
and make a wrapper for the Trim case:
static bool is_trim_arg(unsigned int arg)
{
return (arg & MMC_TRIM_OR_DISCARD_ARGS) && arg != MMC_DISCARD_ARG;
}
> Signed-off-by: Christian Loehle <cloehle@hyperstone.com>
> ---
> drivers/mmc/core/core.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/mmc/core/core.c b/drivers/mmc/core/core.c
> index 95fa8fb1d45f..507005211529 100644
> --- a/drivers/mmc/core/core.c
> +++ b/drivers/mmc/core/core.c
> @@ -1761,7 +1761,8 @@ int mmc_erase(struct mmc_card *card, unsigned int from, unsigned int nr,
> return -EOPNOTSUPP;
>
> if (mmc_card_mmc(card) && (arg & MMC_TRIM_ARGS) &&
> - !(card->ext_csd.sec_feature_support & EXT_CSD_SEC_GB_CL_EN))
> + !(card->ext_csd.sec_feature_support & EXT_CSD_SEC_GB_CL_EN) &&
> + arg != MMC_DISCARD_ARG)
> return -EOPNOTSUPP;
>
> if (arg == MMC_SECURE_ERASE_ARG) {
prev parent reply other threads:[~2022-11-17 8:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-14 13:26 [PATCH] mmc: core: Do not require secure trim for discard Christian Löhle
2022-11-17 8:19 ` Adrian Hunter [this message]
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=bf2c46b3-1117-55dd-ed89-7f4d3ff37b7e@intel.com \
--to=adrian.hunter@intel.com \
--cc=CLoehle@hyperstone.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--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