From: Krishna Konda <kkonda@codeaurora.org>
To: "linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>
Subject: Secure Trim vs Discard & Sanitize
Date: Fri, 22 May 2015 11:30:42 -0700 [thread overview]
Message-ID: <555F75D2.4020501@codeaurora.org> (raw)
The eMMC 4.5 and later specifications mention that the "Secure Erase"
and "Secure Trim" operations are not meant for eMMC 4.5 and later
devices but the driver still performs those operations on when block
layer issues a SECDISCARD (or REQ_DISCARD|REQ_SECURE) request.
I dont know why the driver did not move to TRIM + SANITIZE or DISCARD +
SANITIZE and I could not find any email discussions about this.
I have seen the patches that provide sanitize via ioctls but I am more
interested if the driver should use the newer commands and should it
invoke sanitize when performing a secure discard operation..
--
Thanks,
Krishna Konda
-----------------------------------------------------------------------
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
-----------------------------------------------------------------------
reply other threads:[~2015-05-22 18:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=555F75D2.4020501@codeaurora.org \
--to=kkonda@codeaurora.org \
--cc=linux-mmc@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;
as well as URLs for NNTP newsgroup(s).