On Wed, Jun 28, 2017 at 04:35:11PM +0200, Christoph Hellwig wrote: > On Sat, May 27, 2017 at 08:32:39PM +0100, Al Viro wrote: > > On Sat, May 27, 2017 at 11:16:44AM +0300, Christoph Hellwig wrote: > > > Hi Al, > > > > > > this series cleans up how we implement the various vectored read and write > > > syscalls, as well as the internal iov_iter based APIs. It then switches > > > nfsd to use vfs_iter_read/write which cleans up nfsd. Note that all > > > exportable file systems already implement ->read_iter and ->write_iter > > > anyway. > > > > 1--5 and 7--10 applied. > > Yet these changes don't seem to be in linux-next. Where did you apply > them to? #work.read_write, as part of #work.uaccess. I apologize for being late with #for-next this cycle (putting it very mildly); hopefull I'll have something working by tonight. Hell, quite a bit is still a tangled mess in local queues... ;-/ -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
