Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp422386imm; Tue, 31 Jul 2018 22:07:13 -0700 (PDT) X-Google-Smtp-Source: AAOMgpenyLDpY2B2q7A4UE+64mWeoRSq1gZhcWUHslzYZ2v9P0wM+GUbWTNPSm+4Yf45EaOqzxrM X-Received: by 2002:a63:da04:: with SMTP id c4-v6mr22197834pgh.398.1533100033250; Tue, 31 Jul 2018 22:07:13 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1533100033; cv=none; d=google.com; s=arc-20160816; b=MtjMS7Pu+CYae12wkHOal+YwVi07o7sijBMQOBjI8L0dKyeU6GZTVzGpohowPBCDzp 4LLUkek/NQc61mxDDs+niazZlNcYvv9yl+z/iwpv8mIgJLoj/ffyc1KKTMF6gkPq566U 3w6gIKliW+h9yiw91gl9T3QaOgaKZRAgBb3myMAkz8Gw2R+/Z18S3Vdx85EnmAUGE5+C ccTTIU4mtk6lcZrNaDZ1OIiJeLCbL2V/dsHnEY566kneThN6zcjOCdyVCKgkAkkw6R9o T4HCmP136TS0Fs51dBwepTfS1B3xNzK5o7OdcJkCKk3VtFDnNGMIoOuowGP1ZFzxEhBl c1Xw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :references:in-reply-to:mime-version:dkim-signature :arc-authentication-results; bh=dP7eYFy3YOqdeb5zGVmkhoTe6XT5zLGPdXgEgQ535pU=; b=yNc3Ku5ysTSCWiVBRXZ1sfOTK9Mevl5gpRFrFtnJjmIk1kWQna3gPLt3GLUOp/snfi K2jqmtLS3tzBvAAHGEIENTOhf1K6FTrTmJ7ICQOTGZGryZZ5xkbB1fiZDzwuomIanU6P 7Z9N7ea5nCFNRqeJlbFFWEeTr/BxUHUH7Ifx8llM0lAu3ZCPGFjdBafoYr0KrBox0+D9 fGRT5Y4MIwPMl1LF7KBNRW3zJXfyo8gmZZGesk2oPkZ+spSRuiJzqtFHRzZK2yERBAa7 jKm6sSlh8X9aHIRT/yiZviKUpTfs9lzEGnVlJNeGlJL56Ha+oNWw9aPz9PuZA5odOz92 x5Ng== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=Jx6MPWGF; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id x18-v6si13631947pll.88.2018.07.31.22.06.35; Tue, 31 Jul 2018 22:07:13 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=Jx6MPWGF; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1733043AbeHAGq2 (ORCPT + 99 others); Wed, 1 Aug 2018 02:46:28 -0400 Received: from mail-yw0-f179.google.com ([209.85.161.179]:37405 "EHLO mail-yw0-f179.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726960AbeHAGq2 (ORCPT ); Wed, 1 Aug 2018 02:46:28 -0400 Received: by mail-yw0-f179.google.com with SMTP id w76-v6so6717555ywg.4 for ; Tue, 31 Jul 2018 22:02:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=dP7eYFy3YOqdeb5zGVmkhoTe6XT5zLGPdXgEgQ535pU=; b=Jx6MPWGFbDUOFrMP9kixhf3qwyaRRWbWymM2cRJxLhno8FvJIGlS5zQvzSg4fpXuMv 8jbzQpvdXLMLyzbC895UZXXyVWlJxtPk4CcviJHTs0PyGJxmtSi7B6VKRF5tAXXNiX++ Nzqejk4J3T4YTWVESGdvoqyxekA8929vnDlnrxAyn3n7yFcnYjzsoezv2KFOvDdGfd9r ivwvu5oQp1fyFp1dScFu+O2991bbpEn+m2ORwQ12GzKmo013h3CG6VviHyE7rPWvCOvE 3KtoWE099OtBpnTVuuNY9fhIW4ji4xpH4GsbB3y1mNX8j9RJSLCf0Us3O1cAiu6IMPA+ 7fDw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=dP7eYFy3YOqdeb5zGVmkhoTe6XT5zLGPdXgEgQ535pU=; b=GJz1kTsz5O6zM9LjK8zotw+UcpT3oPvITryE1z/IlUUQtNW3ASWJv9kgF05fjPz1Nr ftza61i7WAAUIMuvM8lS/mnlh0T77m+Gf8Y9kWkVi8JG27T1BOdW+n3Li9ssSG2kYyZl FplPZQrjSXXbUiiN+QTwPFH4rUMoUa7u2yCZPmkXzfwe6+sB8xPXTaO6fvDrpGmiDDsf xTOlKTXn7mhHXHhVD61LfmdWSH8is9dMr5R4dAdlLTJU6yzI7adX10vEr9vG4w6Cyh1p 9WvmeBqMrYCRksZoPTgNLiAfsxTqP6HFhpSCYGQLywh2vK6ze3wzT6Hmy38GYCh5o0pQ jB1g== X-Gm-Message-State: AOUpUlEIZZmsxGCUIQbsWCLa9AhCKi8nKKsvYNa8ARSVVhfM/pnly7Bi P2aohLsw2N4mUcLnSrQfV9cgD4YIK8K9WwcItHQ= X-Received: by 2002:a81:8085:: with SMTP id q127-v6mr12105073ywf.180.1533099766221; Tue, 31 Jul 2018 22:02:46 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a81:3007:0:0:0:0:0 with HTTP; Tue, 31 Jul 2018 22:02:45 -0700 (PDT) In-Reply-To: References: From: Jeff Chua Date: Wed, 1 Aug 2018 13:02:45 +0800 Message-ID: Subject: Re: How to secure erase PCI-E NVME SSD connected via USB3? To: Ming Lei Cc: lkml Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jul 31, 2018 at 7:07 PM, Ming Lei wrote: > On Sun, Jul 29, 2018 at 5:09 PM, Jeff Chua wrote: >> I'm testing the USB3-to-PCI-E NVME SSD. It's works using uas module, >> recognized it as /dev/sda. >> >> Since it's an USB device, the nvme-cli tools won't work, nor does >> hdparm, as it's a NVME SSD. >> >> So, how to secure-erase the NVME SSD connected via the JMS583 chip? > > You may try 'blkdiscard --secure' and see if you are luck. Interesting, will try that. Thanks for the pointer. Jeff.