linux-kernel - [PATCHv2 0/2] NVMe namespace identification

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Wed,  9 Dec 2015 11:42:55 -0700
From:	Keith Busch <keith.busch@...el.com>
To:	linux-nvme@...ts.infradead.org, LKML <linux-kernel@...r.kernel.org>
Cc:	Matthew Wilcox <willy@...ux.intel.com>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Jens Axboe <axboe@...com>,
	Christoph Hellwig <hch@...radead.org>,
	Dan Williams <dan.j.williams@...el.com>,
	Keith Busch <keith.busch@...el.com>
Subject: [PATCHv2 0/2] NVMe namespace identification

Here's version 2 exposing unique namespace identification to sysfs.

This is simpler thanks to feedback from Willy, Christoph, and Dan.

There are two identification attributes displayed in ASCII instead of
binary. Each method has its own file so parsers will know the format.

The first patch in the series adds a new print format since EUI-64
didn't have a specifier. It's essentially an extented MAC identifier,
so appending a specifier for the longer format to that.

I don't know who owns lib/vsprintf, so copying Greg & LKML.

Keith Busch (2):
  Print: Add print format for 8-byte EUI-64 type
  NVMe: Expose namespace identity attribute to sysfs

 Documentation/printk-formats.txt | 13 +++++++--
 drivers/nvme/host/core.c         | 60 ++++++++++++++++++++++++++++++++++++++--
 drivers/nvme/host/nvme.h         |  3 ++
 lib/vsprintf.c                   | 17 ++++++++----
 4 files changed, 83 insertions(+), 10 deletions(-)

-- 
2.6.2.307.g37023ba

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/