From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1764210AbcLTPjr (ORCPT ); Tue, 20 Dec 2016 10:39:47 -0500 Received: from mga11.intel.com ([192.55.52.93]:25619 "EHLO mga11.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1763678AbcLTPjp (ORCPT ); Tue, 20 Dec 2016 10:39:45 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.33,379,1477983600"; d="scan'208";a="20764656" Date: Tue, 20 Dec 2016 10:49:16 -0500 From: Keith Busch To: Christoph Hellwig Cc: Scott Bauer , linux-nvme@lists.infradead.org, Rafael.Antognolli@intel.com, axboe@fb.com, jonathan.derrick@intel.com, viro@zeniv.linux.org.uk, linux-kernel@vger.kernel.org, sagi@grimberg.me Subject: Re: [PATCH v3 4/5] nvme: Implement resume_from_suspend and SED Allocation code. Message-ID: <20161220154916.GC10634@localhost.localdomain> References: <1482176149-2257-1-git-send-email-scott.bauer@intel.com> <1482176149-2257-5-git-send-email-scott.bauer@intel.com> <20161219215954.GB10634@localhost.localdomain> <20161219222311.GA2056@sbauer-Z170X-UD5> <20161220061744.GB4765@infradead.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20161220061744.GB4765@infradead.org> User-Agent: Mutt/1.7.0 (2016-08-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Dec 19, 2016 at 10:17:44PM -0800, Christoph Hellwig wrote: > As far as I can tell Security Send / Receive has always been intended to > apply to the whole controller, even if that's something I would not > personally think is a good idea. NVMe security commands required the namespace ID since the very beginning. It's currently documented in figure 42 of section 5, "Namespace Identifier Used" column. From mboxrd@z Thu Jan 1 00:00:00 1970 From: keith.busch@intel.com (Keith Busch) Date: Tue, 20 Dec 2016 10:49:16 -0500 Subject: [PATCH v3 4/5] nvme: Implement resume_from_suspend and SED Allocation code. In-Reply-To: <20161220061744.GB4765@infradead.org> References: <1482176149-2257-1-git-send-email-scott.bauer@intel.com> <1482176149-2257-5-git-send-email-scott.bauer@intel.com> <20161219215954.GB10634@localhost.localdomain> <20161219222311.GA2056@sbauer-Z170X-UD5> <20161220061744.GB4765@infradead.org> Message-ID: <20161220154916.GC10634@localhost.localdomain> On Mon, Dec 19, 2016@10:17:44PM -0800, Christoph Hellwig wrote: > As far as I can tell Security Send / Receive has always been intended to > apply to the whole controller, even if that's something I would not > personally think is a good idea. NVMe security commands required the namespace ID since the very beginning. It's currently documented in figure 42 of section 5, "Namespace Identifier Used" column.