From: mwilck@suse.com (Martin Wilck)
Subject: [PATCH 3/3] nvme: wwid_show: copy hex string verbatim
Date: Fri, 14 Jul 2017 11:58:16 +0200 [thread overview]
Message-ID: <1500026296.4808.8.camel@suse.com> (raw)
In-Reply-To: <20170714075451.GD17877@lst.de>
On Fri, 2017-07-14@09:54 +0200, Christoph Hellwig wrote:
> On Fri, Jul 14, 2017@12:25:33AM +0200, Martin Wilck wrote:
> > If the serial number is a series of hex digits (as usual for the
> > Linux target), there's no need to encode it in hex once more.
> > This will improve the readability of NVME wwids for users.
>
> NAK, this will break existing device identifiers.
>
If this is what you think, you must also NAK my patch 2/3, because
stripping the 0-bytes also changes how the WWID is presented to user
space. For example
nvme.0000-3163653363666438366239656630386200-
4c696e75780000000000000000000000000000000000000000000000000000000000000
000000000-00000001
becomes after 2/3:
nvme.0000-31636533636664383662396566303862-4c696e7578-00000001
3/3 would change this again to
nvme.0000-1ce3cfd86b9ef08b-4c696e7578-00000001
and Keith's proposal would change it to
nvme.0000-1ce3cfd86b9ef08b-Linux-00000001
User space that relies on the string in the first format would break
already with 2/3. However, multipath, which is probably the main
consumer of the WWID for practical purposes, can't handle the overlong
format anyway (I'm preparing a patch series to fix that).
Therefore, please think twice. It may be worthwhile to accept an
exception to the API stability rule here. Some people will be bitten,
but we will have a saner WWID format in the future. Of course, if this
is to be changed, we'd better do it asap.
Note also that this identifier is volatile for Linux targets anyway,
as the serial number changes between target reboots (I'm aware of
Johannes' recent attempt to change this, but again this is going to be
a configuration that the storage admin must actively apply).
As I wrote in my other mail, if API stability prevails, let's introduce
a new attribute with cleaner format.
Martin
--
Dr. Martin Wilck <mwilck at suse.com>, Tel. +49 (0)911 74053 2107
SUSE Linux GmbH, GF: Felix Imend?rffer, Jane Smithard, Graham Norton
HRB 21284 (AG N?rnberg)
next prev parent reply other threads:[~2017-07-14 9:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-13 22:25 [PATCH 0/3] Improve readbility of NVME "wwid" attribute Martin Wilck
2017-07-13 22:25 ` [PATCH 1/3] nvmet: identify controller: improve standard compliance Martin Wilck
2017-07-14 7:54 ` Christoph Hellwig
2017-07-13 22:25 ` [PATCH 2/3] nvme: wwid_show: strip trailing 0-bytes Martin Wilck
2017-07-14 7:54 ` Christoph Hellwig
2017-07-13 22:25 ` [PATCH 3/3] nvme: wwid_show: copy hex string verbatim Martin Wilck
2017-07-14 7:54 ` Christoph Hellwig
2017-07-14 9:58 ` Martin Wilck [this message]
2017-07-14 12:30 ` Christoph Hellwig
2017-07-14 19:40 ` Martin Wilck
2017-07-15 8:46 ` Christoph Hellwig
2017-07-17 6:12 ` Hannes Reinecke
2017-07-13 22:57 ` [PATCH 0/3] Improve readbility of NVME "wwid" attribute Keith Busch
2017-07-14 7:54 ` Martin Wilck
2017-07-14 7:57 ` Christoph Hellwig
2017-07-14 7:56 ` Christoph Hellwig
2017-07-14 9:41 ` Martin Wilck
2017-07-14 12:28 ` Christoph Hellwig
2017-07-14 7:53 ` Christoph Hellwig
2017-07-14 8:54 ` Martin Wilck
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1500026296.4808.8.camel@suse.com \
--to=mwilck@suse.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.