| 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: Sun, 16 Mar 2008 13:38:18 -0800 From: Daniel Phillips <phillips@...nq.net> To: "Alan D. Brunelle" <Alan.Brunelle@...com> Cc: linux-kernel@...r.kernel.org Subject: Re: [RFC] Stacking bio support On Friday 14 March 2008 06:59, Alan D. Brunelle wrote: > I was able to get the first 3 patches ported to the stable tree of > 2.6.23, but there were compilation errors - fixed in the 4th patch > in the stream I'll post next. Regardless of that, it still failed > to boot on a 2-way AMD64. Do you have a set of these patches that > builds correctly & boots! :-) Here you are: http://code.google.com/p/zumastor/source/browse/www/lvm3/bio.single.alloc-2.6.24.3 http://code.google.com/p/zumastor/source/browse/www/lvm3/bio.hide.endio-2.6.24.3 http://code.google.com/p/zumastor/source/browse/www/lvm3/bio.stack-2.6.24.3 http://code.google.com/p/zumastor/source/browse/www/lvm3/dm.reduce.allocs-2.6.24.3 This compiles and boots for me, though I only tried device mapper under UML, and then only lightly. It would be nice to see some reports on the stability on this, one way or the other. Next move is to clean up __clone_and_map the rest of the way. Thanks for your merge. Not easy, hmm? The mainline bio changes generated a bunch of tracking work, but they are sensible changes so no regrets (the bogus endio bytes parameter and int return are gone). Now... it appears to me that bi_size is an entirely redundant field, so while we are turfing bio junk out... Regards, Daniel -- 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