Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp5009434imm; Tue, 31 Jul 2018 04:08:57 -0700 (PDT) X-Google-Smtp-Source: AAOMgpcGpSM6c9W160ujNLLinliBaMcsLVfwYljmLlshLkrRE3BuF+eZXV0mHUB/GI4m9cdVYIPC X-Received: by 2002:a63:951e:: with SMTP id p30-v6mr20016561pgd.318.1533035337390; Tue, 31 Jul 2018 04:08:57 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1533035337; cv=none; d=google.com; s=arc-20160816; b=ReU7IUDwpakNz5CrLH6op5IajsuoQlpedlR+kt+Nj3L0rd/Emzr0uqqr0izAycNWPD DQdj51EC5adFXneOOO6ZLsPl0uu8Jc9Ep2AbO01GivQ6PqvEwd6LbRK3nz94LGcl/tiD 8WUS36UTyKX+BrMnHS/I2x3z49nP2xOJwPYFlSaPlp5dKtmLAuOBCm0jejDsK79D0Elh fv4lCp4icAiDLBMayG9RpFi/7yGW3f37eZ+tTnhzLDHd7GI7uDX8D4beo27F7VCZIDox nTTsQ4H3UKbEWwSWR0D7emvKboOcM++JbiLkkbLjfFHJ228SizQ2Bd1v56QiXDL1HMjA yncA== 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=8lWbHqiHOGiqhGb369tzpBgXP2BLu6gr3nc0Vfjql1I=; b=Da19Ja60u0jPOMKDtRAmrt+iua6fOUSBZ16Gm5afWsYDTCxXhNDnuy52l/Ijw2wMZI QCZ4YppbqsxYpMl04Sk0/tV1QFNJmrUlLJvqOyaFsFhGQf2QR4V6YdRV/MdZ+dCRjVjf 2u6Q/pJqvKXPHZjXVDeJVukDA/OTBHvq5DvlYm6qjEjho6+shu9FrMpxmbFQp7o6rkj1 OynPCXoCGuryoVv1OypAYY3mW8uZEsRqzeoARewI6uFGy4FD8SftbT7JeufIIE6yLfZg RBqjjh8hJ/r8mYSWyI/lqIXf8pTX7P5PQTWm9X75XwmEhOf47Ytq0ghDqCx3TNKa8QjI Kvrg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=ZP1VZLau; 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 101-v6si11749663ple.113.2018.07.31.04.08.42; Tue, 31 Jul 2018 04:08:57 -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=ZP1VZLau; 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 S1732007AbeGaMra (ORCPT + 99 others); Tue, 31 Jul 2018 08:47:30 -0400 Received: from mail-wr1-f43.google.com ([209.85.221.43]:39949 "EHLO mail-wr1-f43.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731503AbeGaMra (ORCPT ); Tue, 31 Jul 2018 08:47:30 -0400 Received: by mail-wr1-f43.google.com with SMTP id h15-v6so16179255wrs.7 for ; Tue, 31 Jul 2018 04:07:42 -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=8lWbHqiHOGiqhGb369tzpBgXP2BLu6gr3nc0Vfjql1I=; b=ZP1VZLauEG9yZbaTRYz7yqlspAvfQhKKykv7hrBF3lIbMUjWfagp0Ez+y74p9EWJ92 fhEvgUAJskbSMbGe4VA9hH/6CcouO86y2D6++eVcERTp878o+7Pzp8JysVj+qOmayVOM ahU/Bc5FxhDUMLREQJJyDwePtA2sTOGxSKxZGDXkKDr0Iue8KIclIFeyAGCYRqpAPjcI kvc7z2eL3mCcqp9a4wwucpBzDjyUYPfwizEOPYYs6Yi+FWSWE97VDxaJQNx3e1QvaDul ft+hz42WcCeu7lzYt+CQllA8/InrbnQ5KV4P9gHQ6nPyN7Mfn6s4m4hs2uwR9fLkgORd o5/Q== 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=8lWbHqiHOGiqhGb369tzpBgXP2BLu6gr3nc0Vfjql1I=; b=ZuLm957mKfA5L04PrHHFYObU0aQWQ0Uy4c/gXjZ2869DvPWhw6utyjziOcSQI51acj HPXY0+K4fpmf0usB2yWKf2r06gfjrRZkAwKdqTnoXty5YMvwhAAiMxHPbMwX63ybf6rt oeS6LpYWockWPJaoHw5vH2/NzWpvGDvq1lDTNO6f+LN2hQwhvKUG5e2Ki76QZlxdvbMj h1mPd2vnVpku+kugNotDj/g8btctmBu2dGOj85SWcwGawug8HNXjzM0D1WjKx3IMQC2O H/jfO3ukrGrSzas3qIv6dFPVJnvpLbWFJh+VEdWHuENYO6uFxvQUuKOkutNp2vMdnJWk L+ow== X-Gm-Message-State: AOUpUlFQXv+C2h2t6uJAGDd4wgvxt+LIUfJx6gTi/NEuk7RyFC2s16f6 gCbqP76mVvYPhZa7xKx4t9AcwQuFEv13j8xzqWs= X-Received: by 2002:adf:83c6:: with SMTP id 64-v6mr20051253wre.5.1533035261546; Tue, 31 Jul 2018 04:07:41 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a1c:9c8:0:0:0:0:0 with HTTP; Tue, 31 Jul 2018 04:07:40 -0700 (PDT) In-Reply-To: References: From: Ming Lei Date: Tue, 31 Jul 2018 19:07:40 +0800 Message-ID: Subject: Re: How to secure erase PCI-E NVME SSD connected via USB3? To: Jeff Chua 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 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. Thanks, Ming Lei