Re: NFSACL broken from 3.13 to 3.14

From: Christoph Hellwig
Date: Thu May 15 2014 - 11:33:15 EST


On Thu, May 15, 2014 at 04:25:47PM +0200, JA Magall??n wrote:
> I mount homes from a Solaris 10 server, via NFSv3. Solaris nfs has a special
> sideband server on a port for NFS to check ACLs. With previous version of
> kernel (3.13.10 was the latest I check), I need no special option to mount
> Solaris shares. With 3.14, it began to give errors, directories created
> with mkdir returned error, files got created but truncated to 0 size...
> (now I have 3.14.3).
>
> I solved it adding the 'noacl' option to Solaris mount entries in autofs,
> so the linux clients don't use the sideband protocol.
>
> As I have read, NFSACL usage is negotitated between client and server.
> Something has changed and the negotiation fails, perhaps ?

We have some pretty bug ACL changes in 3.14. I've tested it against a
Linux server, but don't have a Solaris server available. Do you have
something like strace or wireshark traces to show differences between
the versions?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/