| 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: Wed, 11 Jul 2007 09:27:40 +1000 From: Paul Mackerras <paulus@...ba.org> To: Jeff Garzik <jeff@...zik.org> Cc: Andrew Morton <akpm@...ux-foundation.org>, Theodore Tso <tytso@....edu>, linux-kernel@...r.kernel.org, Amit Arora <aarora@...ibm.com>, Andi Kleen <ak@...e.de>, Benjamin Herrenschmidt <benh@...nel.crashing.org>, Arnd Bergmann <arnd@...db.de>, "Luck, Tony" <tony.luck@...el.com>, Heiko Carstens <heiko.carstens@...ibm.com>, Martin Schwidefsky <schwidefsky@...ibm.com>, Mark Fasheh <mark.fasheh@...cle.com>, linux-arch@...r.kernel.org Subject: Re: fallocate-implementation-on-i86-x86_64-and-powerpc.patch Jeff Garzik writes: > Andrew Morton wrote: > > So I dropped everything. Let's start again from scratch. I'd suggest that > > for now we go with just an i386/x86_64 implementation, let the arch > > maintainers wire things up when that has settled down. > > > It's my observation that that plan usually works the best. Arch ... except when the initial implementer picks an argument order which doesn't work on some archs, as happened with sys_sync_file_range. That is also the case with fallocate IIRC. We did come up with an order that worked for everybody, but that discussion seemed to get totally ignored by the ext4 developers. Paul. - 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