NFSACL broken from 3.13 to 3.14

[JA MagallÃn]

Hi...

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 ?

Any idea ?

TIA

--
J.A. Magallon <jamagallonn()gmail!com>     \               Winter is coming...
--
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/