Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp2738815imm;
        Sun, 29 Jul 2018 02:10:54 -0700 (PDT)
X-Google-Smtp-Source: AAOMgpfb18crxZ9AiSVSg1Qbx9HDybkOKryHGbklGamBVoe/SrkklymIDVHwh4I3mWM1XZdP24es
X-Received: by 2002:a63:f:: with SMTP id 15-v6mr12232833pga.430.1532855454801;
        Sun, 29 Jul 2018 02:10:54 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1532855454; cv=none;
        d=google.com; s=arc-20160816;
        b=faeI9SSVpDjVJt21vswownEbetNQ6mRtUcP4KRNKuh4LTEXR58B2/Y06dyMPq5hdJg
         kticEnPWvqJT0Q2hvhrJysGTFguApuQC6vLFzgmK3JT+qQ/M5SOVYsMI+XlRcIVI192l
         VqMt/kbQb9sG9spFlMlx25hRvZhFmyMG/sJYFbmRHcg09q8DIo6eutNBMDrBBkNBCH55
         IHVCi+kEOPx9V5UDUUjsdvZyBrF40MSX6uwGRm0oS2fVQM7ffMXYx1v01l5veT/QxIn6
         YUEnuCEDewjGyx6wox8lNVtchrMRRpybYZzGoAxjhsde3AZn2iuImRxcG9DqZVwzcWoU
         MY7Q==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816;
        h=list-id:precedence:sender:to:subject:message-id:date:from
         :mime-version:dkim-signature:arc-authentication-results;
        bh=FN9aD4W60jNdb/kPBFrOauRS3YTaIGCx31hwoikrBmE=;
        b=waXbM7EX5165R6kMFJvzfuv364sTCy8D7+qt//s14YEG4yYEM1h/yE5/7/o1A06QX4
         4zsltU5oGk0Wfdq2cXoq2HL6VJtOJp333d2MMKKiOscKE06ExxvPKNHmIURp2mgOw0Tc
         Sk8Yo8Rcxhq6nHB6A9Bqdk43n7ujcFhFLVopscmWJbSI9XVqn/JQJ7cBZUDMaELfDDg3
         k5fsHdZ33IRfDr+pL6mVGLd71qZlgRaHT0VWwlPj+fScom15wKyAahbjwjv8Fup0Rbd9
         E3zUwlQuIn/bLSb9apAjbAH92e0siaRluLiia/A36SxCZ2EGIHU0GNbXukHGGZAuxxzs
         bBqw==
ARC-Authentication-Results: i=1; mx.google.com;
       dkim=pass header.i=@gmail.com header.s=20161025 header.b=Gd2hFNTu;
       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: <linux-kernel-owner@vger.kernel.org>
Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67])
        by mx.google.com with ESMTP id m24-v6si7644389pgl.452.2018.07.29.02.10.39;
        Sun, 29 Jul 2018 02:10:54 -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=Gd2hFNTu;
       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 S1726294AbeG2Kjf (ORCPT <rfc822;kernelgary@gmail.com>
        + 99 others); Sun, 29 Jul 2018 06:39:35 -0400
Received: from mail-yb0-f181.google.com ([209.85.213.181]:34545 "EHLO
        mail-yb0-f181.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1726170AbeG2Kje (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Sun, 29 Jul 2018 06:39:34 -0400
Received: by mail-yb0-f181.google.com with SMTP id e9-v6so3662144ybq.1
        for <linux-kernel@vger.kernel.org>; Sun, 29 Jul 2018 02:09:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20161025;
        h=mime-version:from:date:message-id:subject:to;
        bh=FN9aD4W60jNdb/kPBFrOauRS3YTaIGCx31hwoikrBmE=;
        b=Gd2hFNTugwnrhRl1/oXHod4ZsbZWsrUZPdpGHlCOR8OxIeHwTlMIRkrZJdUfOqrOA1
         ZJFGCp80UZ9/v+w8wmuvTHJaG1eFiL3rtjAokbrlVACe6E7KZlawOBntvoKnOPHAhncp
         IDaULItX8vATjkD0AvCCPUzCfEEPLzLUC0Q9vEmSo7VnY3SvEBX2BgPPLB8sx27wfr8f
         uhDMPpejeiQ3R5qpL2AI8qBg+UqMLzhrbgDOkgaoT4Y5X7GdjasYlu00bQ67FPw7NiP8
         TqfAogCDngXR3lhs2o3+8d/UgRFs2bSaWHY74a1XDvXJCC0UB+hclUN8lGVvDphz2Wkw
         ssHA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20161025;
        h=x-gm-message-state:mime-version:from:date:message-id:subject:to;
        bh=FN9aD4W60jNdb/kPBFrOauRS3YTaIGCx31hwoikrBmE=;
        b=r/1A9PVo+F/hMWMS4ISJH70AIda2n3VL1QRn1usS5zq4t8cm9rMoj7XPDvE1S7GSu2
         hN5DDLVAhnmky7IIBUqMRgbbiNUPYKziIdkTIJ26MlPVoW+xZUP3NezbOeazxj2rjnL8
         7IrMdfrhor3Xagli14PPJKuxAZU1IhCgJXLg/l8msbfOxKJ8H+09/OYd55ULYd5vDXJg
         dXJ1bIEy1BpbGRza9yoEOZxLefGEP+WEFnvBrwiymvEdO6NXoq9i7Yajt23w6rlrDQMq
         LfpPrhmhJYvB2hXvqQXKP/ycJ7145i2h4bePD0pSOYMtnqFmlqkEtr7Kg1hhsK+R2XDo
         BQpg==
X-Gm-Message-State: AOUpUlEA3x87w+fDTNHzqLf+Jb1J3ywaEj32Kgol66LpZvjm/F2s770k
        nAVK2TyMBKEGov3ySfvIVLa6Ts9Y2svizYXvDRAYGrSm
X-Received: by 2002:a25:ef04:: with SMTP id g4-v6mr6829991ybd.223.1532855389139;
 Sun, 29 Jul 2018 02:09:49 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a81:3007:0:0:0:0:0 with HTTP; Sun, 29 Jul 2018 02:09:48
 -0700 (PDT)
From:   Jeff Chua <jeff.chua.linux@gmail.com>
Date:   Sun, 29 Jul 2018 17:09:48 +0800
Message-ID: <CAAJw_ZuQXrYaEu9_pXWtoDpUjR2au1gGT_FP9F1e1Y7veHSz2Q@mail.gmail.com>
Subject: How to secure erase PCI-E NVME SSD connected via USB3?
To:     lkml <linux-kernel@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

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?

Thanks,
Jeff.