From: Jens Axboe <axboe@kernel.dk>
To: Asai Thambi SP <asamymuthupa@micron.com>
Cc: linux-kernel@vger.kernel.org, Sam Bradshaw <sbradshaw@micron.com>,
Selvan Mani <smani@micron.com>
Subject: Re: [PATCH 8/9] mtip32xx: abort secure erase operation if the device is mounted
Date: Tue, 12 May 2015 11:46:30 -0400 [thread overview]
Message-ID: <55522056.9050102@kernel.dk> (raw)
In-Reply-To: <55513388.9030600@micron.com>
On 05/11/2015 06:56 PM, Asai Thambi SP wrote:
> Signed-off-by: Sam Bradshaw <sbradshaw@micron.com>
> Signed-off-by: Asai Thambi S P <asamymuthupa@micron.com>
> ---
> drivers/block/mtip32xx/mtip32xx.c | 12 ++++++++++++
> 1 files changed, 12 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/block/mtip32xx/mtip32xx.c b/drivers/block/mtip32xx/mtip32xx.c
> index 0b223e3..f8c12e1 100644
> --- a/drivers/block/mtip32xx/mtip32xx.c
> +++ b/drivers/block/mtip32xx/mtip32xx.c
> @@ -2147,6 +2147,18 @@ static int exec_drive_taskfile(struct driver_data *dd,
> fis.lba_hi,
> fis.device);
>
> + /* Check for secure erase while fs mounted */
> + if ((fis.command == ATA_CMD_SEC_ERASE_PREP) ||
> + (fis.command == ATA_CMD_SEC_ERASE_UNIT) ||
> + (fis.command == 0xFC && fis.features == 0x12)) {
> + if (dd->bdev && dd->bdev->bd_holders > 0) {
> + dev_warn(&dd->pdev->dev, "Drive erase aborted due to non-zero refcount (%d)\n",
> + dd->bdev->bd_holders);
> + err = -ERESTARTSYS;
> + goto abort;
> + }
> + }
I don't like this. If you want to do something like this, why not claim
before these commands and unclaim after? If the claim fails, fail the
command.
--
Jens Axboe
next prev parent reply other threads:[~2015-05-12 15:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-11 22:56 [PATCH 8/9] mtip32xx: abort secure erase operation if the device is mounted Asai Thambi SP
2015-05-12 15:46 ` Jens Axboe [this message]
2015-05-13 0:39 ` Asai Thambi SP
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=55522056.9050102@kernel.dk \
--to=axboe@kernel.dk \
--cc=asamymuthupa@micron.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sbradshaw@micron.com \
--cc=smani@micron.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