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
| ||
|
Date: Fri, 16 Jun 2017 11:58:37 +0200 From: Christoph Hellwig <hch@....de> To: Johannes Thumshirn <jthumshirn@...e.de> Cc: Christoph Hellwig <hch@....de>, Sagi Grimberg <sagi@...mberg.me>, Linux Kernel Mailinglist <linux-kernel@...r.kernel.org>, Linux NVMe Mailinglist <linux-nvme@...ts.infradead.org>, Keith Busch <keith.busch@...el.com>, Hannes Reinecke <hare@...e.de>, Max Gurtovoy <maxg@...lanox.com> Subject: Re: [PATCH v6 00/10] Implement NVMe Namespace Descriptor Identification On Fri, Jun 16, 2017 at 11:48:32AM +0200, Johannes Thumshirn wrote: > On 06/16/2017 11:40 AM, Christoph Hellwig wrote: > > On Fri, Jun 16, 2017 at 10:20:04AM +0200, Johannes Thumshirn wrote: > >> Strange, as I tested with nvme-loop all the time... > > > > Yeah, it's actually there, but for some reason find on sysfs > > behaves strange: > > > > root@...tvm:~# find /sys -name uuid > > root@...tvm:~# cat /sys/class/nvme/nvme2/nvme2n1/uuid > > 6665a65b-f42f-469b-800e-a047238649eb > > Wasn't there something that find on sysfs isn't reliable? Looks like it. Which is a pitty. > Anyways, my shock's gone now. Heh. Now we just need the nvme-cli patches to verify it independently :)
Powered by blists - more mailing lists