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: Thu, 7 Nov 2013 23:44:45 -0800 From: Christoph Hellwig <hch@...radead.org> To: Kent Overstreet <kmo@...erainc.com> Cc: Dave Kleikamp <dave.kleikamp@...cle.com>, Stephen Rothwell <sfr@...b.auug.org.au>, Jens Axboe <axboe@...nel.dk>, linux-next@...r.kernel.org, linux-kernel@...r.kernel.org, Zach Brown <zab@...bo.net>, Olof Johansson <olof@...om.net>, Andrew Morton <akpm@...ux-foundation.org> Subject: Re: linux-next: manual merge of the block tree with the tree On Thu, Nov 07, 2013 at 11:39:59PM -0800, Kent Overstreet wrote: > On Thu, Nov 07, 2013 at 11:33:24PM -0800, Christoph Hellwig wrote: > > The changes for direct I/O from kernel space have been in for a long > > time, and they are blocking multiple consumers of the interface from > > getting submitted for about a year now. Even if the guts of the > > direct-io code will get a write based on another patchset from Kent > > that will go on top of the immutable iovec changes we need the > > interfaces now and not another year down the road. > > What else is blocked on this patch series? Honest question. >From me alone: Support for ecryptfs to not double cache. AIO support for target_core_file. To replace code in staging: Removal of the lustre-specific loop driver. And I remember others claiming to want to submit bits, too. -- 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