linux-kernel - NFSACL broken from 3.13 to 3.14

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <536C0306.50202@gmail.com>
Date:	Fri, 09 May 2014 00:19:50 +0200
From:	JA Magallón <jamagallonn@...il.com>
To:	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: NFSACL broken from 3.13 to 3.14

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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/