Re: [GIT PULL] nfsd changes for 4.20

2018-10-31 Thread Trond Myklebust
On Wed, 2018-10-31 at 11:44 -0400, J. Bruce Fields wrote: > Stephen also sent a warning about a merge conflict with the vfs tree > (not merged yet, I think) but I assume that's not as big a deal since > it > should actually show up at merge time, not build time: > > > http://lkml.kernel.or

Re: [GIT PULL] nfsd changes for 4.20

2018-10-31 Thread J. Bruce Fields
On Tue, Oct 30, 2018 at 01:06:58PM -0700, Linus Torvalds wrote: > On Tue, Oct 30, 2018 at 12:55 PM Linus Torvalds > wrote: > > > > Pulled, > > Oh, I take that back. Semantic conflict with locking name change > (recv_lock -> queue_lock) and new code in > >net/sunrpc/xprtrdma/svc_rdma_backchan

Re: [GIT PULL] nfsd changes for 4.20

2018-10-30 Thread Linus Torvalds
On Tue, Oct 30, 2018 at 12:55 PM Linus Torvalds wrote: > > Pulled, Oh, I take that back. Semantic conflict with locking name change (recv_lock -> queue_lock) and new code in net/sunrpc/xprtrdma/svc_rdma_backchannel.c exposed by my build test. And looking around, it was reported in linux-nex

Re: [GIT PULL] nfsd changes for 4.20

2018-10-30 Thread Linus Torvalds
On Tue, Oct 30, 2018 at 12:17 PM J. Bruce Fields wrote: > > Please pull nfsd changes for 4.20: Pulled, Linus

[GIT PULL] nfsd changes for 4.20

2018-10-30 Thread J. Bruce Fields
Please pull nfsd changes for 4.20: git://linux-nfs.org/~bfields/linux.git tags/nfsd-4.20 Olga added support for the NFSv4.2 asynchronous copy protocol. We already supported COPY, by copying a limited amount of data and then returning a short result, letting the client resend. The asynchronous