From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751216AbcFXHhc (ORCPT ); Fri, 24 Jun 2016 03:37:32 -0400 Received: from bombadil.infradead.org ([198.137.202.9]:43290 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750943AbcFXHhb (ORCPT ); Fri, 24 Jun 2016 03:37:31 -0400 Date: Fri, 24 Jun 2016 00:37:28 -0700 From: Christoph Hellwig To: Jethro Beekman Cc: keith.busch@intel.com, axboe@fb.com, linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 0/3] nvme: Don't add namespaces for locked drives Message-ID: <20160624073728.GA30277@infradead.org> References: <20160619230634.17229-1-kernel@jbeekman.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160619230634.17229-1-kernel@jbeekman.nl> User-Agent: Mutt/1.6.1 (2016-04-27) X-SRS-Rewrite: SMTP reverse-path rewritten from by bombadil.infradead.org. See http://www.infradead.org/rpr.html Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Jun 19, 2016 at 04:06:31PM -0700, Jethro Beekman wrote: > Hi all, > > If an NVMe drive is locked with ATA Security, most commands sent to the drive > will fail. This includes commands sent by the kernel upon discovery to probe > for partitions. The failing happens in such a way that trying to do anything > with the drive (e.g. sending an unlock command; unloading the nvme module) is > basically impossible with the high default command timeout. Do you have any spec that defines this ATA security protocol and how it applies to NVMe? The NVMe spec just referes to SPC4 for security protocols, and I haven't been able to find a reference to an ATA security protocol in it either, but I haven't tried hard yet.