| 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
| ||
|
Message-ID: <yq11u134rmt.fsf@sermon.lab.mkp.net> Date: Mon, 23 Dec 2013 08:35:22 -0500 From: "Martin K. Petersen" <mkp@....net> To: Christoph Hellwig <hch@...radead.org> Cc: Jens Axboe <axboe@...nel.dk>, linux-kernel@...r.kernel.org, linux-scsi@...r.kernel.org Subject: Re: status of block-integrity >>>>> "Christoph" == Christoph Hellwig <hch@...radead.org> writes: Christoph> We have the block integrity code to support DIF/DIX in the Christoph> the tree for about 5 and a half years, and we still don't Christoph> have a single consumer of it. What do you mean? If you have a DIX-capable HBA (lpfc, qla2xxx, zfcp) then integrity protection is active from the block layer down. The only code that's not currently being exercised are the tag interleaving functions. I was hoping the FS people would use them for back pointers but nobody seemed to bite. Christoph> Given that we'll have a lot of work to do in this area with Christoph> block multiqueue I think it's time to either kill it off for Christoph> good or make sure we can actually use and test it. I don't understand why multiqueue would require a lot of work? It's just an extra scatterlist per request. And obviously, if there's anything that needs to be done in this area I'll be happy to do so... -- Martin K. Petersen Oracle Linux Engineering -- 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/
Powered by blists - more mailing lists