From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752375AbdGMPQg (ORCPT ); Thu, 13 Jul 2017 11:16:36 -0400 Received: from verein.lst.de ([213.95.11.211]:34475 "EHLO newverein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751193AbdGMPQf (ORCPT ); Thu, 13 Jul 2017 11:16:35 -0400 Date: Thu, 13 Jul 2017 17:16:33 +0200 From: Christoph Hellwig To: Martin Wilck Cc: Johannes Thumshirn , Christoph Hellwig , Sagi Grimberg , Keith Busch , Linux Kernel Mailinglist , Linux NVMe Mailinglist Subject: Re: [PATCH] nvmet: preserve controller serial number between reboots Message-ID: <20170713151633.GA993@lst.de> References: <20170713104806.12353-1-jthumshirn@suse.de> <1499958505.6432.8.camel@suse.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1499958505.6432.8.camel@suse.de> User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jul 13, 2017 at 05:08:25PM +0200, Martin Wilck wrote: > I'm wondering if this should be a write-once attribute. Also, > Once the serial number has been passed on to some host (or maybe only: > while the device is in use by some host), the attribute should probably > be read-only. In practive it should. But I don't think it's worth the extra code just to prevent people from shooting themselves into the foot.