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: Mon, 22 Jun 2015 18:34:53 +0200 From: Christoph Hellwig <hch@....de> To: Dan Williams <dan.j.williams@...el.com> Cc: axboe@...nel.dk, linux-nvdimm@...ts.01.org, boaz@...xistor.com, toshi.kani@...com, Neil Brown <neilb@...e.de>, Greg KH <gregkh@...uxfoundation.org>, linux-kernel@...r.kernel.org, mingo@...nel.org, linux-acpi@...r.kernel.org, linux-fsdevel@...r.kernel.org, hch@....de Subject: Re: [PATCH 02/15] libnvdimm: infrastructure for btt devices FYI, the mess calls into libnvdimm for each register pmem or blk device which then walks partitions to find your btt metadata is an absolutely no go and suggest that the layering is completely fucked up. Please go and revisit it for a sensible model, where the different drivers attach to a nvdimm bus instead of stacking up with a little detour through the block layer. From all that it's pretty clear pmem, blk and btt should be peers in the hierarchy. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists