From: Christoph Hellwig <hch@infradead.org>
To: JA Magall??n <jamagallon@ono.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>, linux-nfs@vger.kernel.org
Subject: Re: NFSACL broken from 3.13 to 3.14
Date: Thu, 15 May 2014 08:33:07 -0700 [thread overview]
Message-ID: <20140515153307.GA9016@infradead.org> (raw)
In-Reply-To: <5374CE6B.6030905@ono.com>
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?
next prev parent reply other threads:[~2014-05-15 15:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-15 14:25 NFSACL broken from 3.13 to 3.14 JA Magallón
2014-05-15 15:33 ` Christoph Hellwig [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-05-08 22:19 JA Magallón
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140515153307.GA9016@infradead.org \
--to=hch@infradead.org \
--cc=jamagallon@ono.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox