linux-kernel - Re: 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>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20140515153307.GA9016@infradead.org>
Date:	Thu, 15 May 2014 08:33:07 -0700
From:	Christoph Hellwig <hch@...radead.org>
To:	JA Magall??n <jamagallon@....com>
Cc:	Linux Kernel <linux-kernel@...r.kernel.org>,
	linux-nfs@...r.kernel.org
Subject: Re: NFSACL broken from 3.13 to 3.14

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