From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751232AbcFXIMk (ORCPT ); Fri, 24 Jun 2016 04:12:40 -0400 Received: from bombadil.infradead.org ([198.137.202.9]:59300 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751101AbcFXIMh (ORCPT ); Fri, 24 Jun 2016 04:12:37 -0400 Date: Fri, 24 Jun 2016 01:12:35 -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 1/3] nvme: When scanning namespaces, make sure the drive is not locked Message-ID: <20160624081235.GA12715@infradead.org> References: <20160619230634.17229-1-kernel@jbeekman.nl> <20160619230634.17229-2-kernel@jbeekman.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160619230634.17229-2-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:32PM -0700, Jethro Beekman wrote: > + if (nvme_security_is_locked(ctrl, id)) { > + nvme_remove_namespaces(ctrl); > + return; > + } Should we print some information for the user that we are ignoring a namespace because it is locked?