Improve readbility of NVME "wwid" attribute
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest3 patches 0 repliesNew
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | nvmet: identify controller: improve standard compliance | +0 | 0 replies | |
| 2/3 | nvme: wwid_show: strip trailing 0-bytes | +0 | 0 replies | |
| 3/3 | nvme: wwid_show: copy hex string verbatim | +0 | 5 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/3] Improve readbility of NVME "wwid" attribute
Quoted 9 lines · Martin Wilck
With the current implementation, the default "fallback" WWID generation code (if no nguid, euid etc. are defined) for Linux NVME host and target results in the following WWID format:
nvme.0000-3163653363666438366239656630386200-4c696e75780000000000000000000000000000000000000000000000000000000000000000000000-00000002
This is not only hard to read, it poses real problems for multipath (dm WWIDs are limited to 128 characters), and it's not fully standards compliant.
What standard? The wwid field is a Linux invention.