linux-kernel - Re: [RFC, PATCH] Extensible AIO interface

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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <yq1sj9w33mq.fsf@sermon.lab.mkp.net>
Date:	Tue, 02 Oct 2012 18:34:05 -0400
From:	"Martin K. Petersen" <martin.petersen@...cle.com>
To:	Kent Overstreet <koverstreet@...gle.com>
Cc:	Zach Brown <zab@...bo.net>, linux-kernel@...r.kernel.org,
	linux-fsdevel@...r.kernel.org, tytso@...gle.com, tj@...nel.org,
	Dave Kleikamp <dave.kleikamp@...cle.com>,
	Dmitry Monakhov <dmonakhov@...nvz.org>,
	"Maxim V. Patlasov" <mpatlasov@...allels.com>,
	michael.mesnier@...el.com, jeffrey.d.skirvin@...el.com,
	Martin Petersen <martin.petersen@...cle.com>
Subject: Re: [RFC, PATCH] Extensible AIO interface

>>>>> "Kent" == Kent Overstreet <koverstreet@...gle.com> writes:

>> Hmm, careful here.  I think that in DIF/DIX the checksums are
>> per-sector, not per IO, right?  That'd mean that the PAGE_SIZE attr
>> limit in this patch would be magically creating different max IO size
>> limits on different architectures.  That doesn't seem great.

Kent> Not just per sector, Per hardware sector. 

Per logical block (or for some devices less).


Kent> For passing around checksums userspace would have to find out the
Kent> hardware sector size and checksum type/size via a different
Kent> interface,

The relevant information is already exported in sysfs. Including the
format, how many bytes of integrity metadata go with how many bytes of
data, etc.

-- 
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/