[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160208151258.GB25111@localhost.localdomain>
Date: Mon, 8 Feb 2016 15:12:58 +0000
From: Keith Busch <keith.busch@...el.com>
To: Christoph Hellwig <hch@....de>
Cc: Sagi Grimberg <sagig@....mellanox.co.il>,
Hannes Reinecke <hare@...e.de>,
James Bottomley <James.Bottomley@...senPartnership.com>,
Jens Axboe <axboe@...nel.dk>, linux-block@...r.kernel.org,
linux-scsi <linux-scsi@...r.kernel.org>,
"linux-nvme@...ts.infradead.org" <linux-nvme@...ts.infradead.org>,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: complete boot failure in 4.5-rc1 caused by nvme: make SG_IO
support optional
On Mon, Feb 08, 2016 at 11:13:50AM +0100, Christoph Hellwig wrote:
> On Mon, Feb 08, 2016 at 12:01:16PM +0200, Sagi Grimberg wrote:
> >
> >> Do we have defined sysfs attributes for NVMe devices nowadays?
> >
> > /sys/block/nvme0n1/uuid
>
> That's only supported for NVMe 1.1 and higher devices, and optional.
> For older or stupid devices we need to support the algorithm based
> on the serial attribute from nvme_fill_device_id_scsi_string() in
> drivers/nvme/host/scsi.c.
It's even worse. NGUID was defined for 1.2 devices and higher. 1.1
devices should have EUI-64 at:
/sys/block/nvmeXnY/eui
1.2 devices will have either uuid or eui (or both).
The majority of devices in circulation today are 1.0, and need to concat
these three entries to make a unique identifier:
/sys/block/nvmeXnY/device/serial
/sys/block/nvmeXnY/device/model
/sys/block/nvmeXnY/nsid
Powered by blists - more mailing lists