On Wed, Oct 22, 2014 at 03:50:15PM -0400, Anna Schumaker wrote:
> > int nfs4_call_sync(struct rpc_clnt *clnt,
> > struct nfs_server *server,
> > struct rpc_message *msg,
> > @@ -8431,7 +8430,8 @@ static const struct nfs4_minor_version_ops nfs_v4_2_minor_ops = {
> > | NFS_CAP_CHANGE_ATTR
> > | NFS_CAP_POSIX_LOCK
> > | NFS_CAP_STATEID_NFSV41
> > - | NFS_CAP_ATOMIC_OPEN_V1,
> > + | NFS_CAP_ATOMIC_OPEN_V1
> > + | NFS_CAP_SEEK,
>
> This looks like it really does add the capability to nfs_v4_2_minor_ops, so I'm not sure how it ended up modifying nfs_v4_1_minor_ops instead. Anyway, I just posted a fix to set the flag in the right place.
Given that the caps were the same before this is something that patch
can easily do when applying patches with a fuzz.
--
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
