From: Andreas Gruenbacher <agruen@suse.de>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Neil Brown <neilb@cse.unsw.edu.au>, Olaf Kirch <okir@suse.de>,
"Andries E. Brouwer" <Andries.Brouwer@cwi.nl>,
Andrew Morton <akpm@osdl.org>
Subject: Re: [patch 11/16] Solaris nfsacl workaround
Date: Thu, 10 Mar 2005 09:16:57 +0100 [thread overview]
Message-ID: <1110442616.25570.2.camel@winden.suse.de> (raw)
In-Reply-To: <1110412619.10804.51.camel@lade.trondhjem.org>
On Thu, 2005-03-10 at 00:56, Trond Myklebust wrote:
> su den 27.02.2005 Klokka 16:22 (+0100) skreiv Andreas Gruenbacher:
> > vanlig tekstdokument vedlegg (nfsacl-solaris-nfsacl-workaround.patch)
> > If the nfs_acl program is available, Solaris clients expect both version
> > 2 and version 3 to be available; RPC_PROG_MISMATCH leads to a mount
> > failure. Fake RPC_PROG_UNAVAIL when asked for nfs_acl version 2.
> >
> > Trond has rejected this patch. I'm not sure how to deal with it in a
> > truly clean way, so probably I won't care and still use this as a vendor
> > patch.
>
> So I've talked to the Solaris implementors about this issue. They said
> that the above behaviour on their clients was a bug that they've
> corrected in Solaris 10.
Thanks for gathering this piece of information.
> Given that very few people are going to be using Solaris clients with
> NFSv2 against a Linux server, and given that there is always the option
> of compiling the server without NFSACL support for those few who need to
> do this, I suggest we just drop this patch.
It's NFSv3 clients that exhibit the strange behavior; else I never would
have run into this bug. For me it's okay to leave out this patch; we'll
still carry it around in our vendor tree for a while though.
Cheers,
--
Andreas Gruenbacher <agruen@suse.de>
SUSE Labs, SUSE LINUX GMBH
next prev parent reply other threads:[~2005-03-10 8:17 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-27 15:22 [patch 00/16] NFSACL protocol extension for NFSv3 Andreas Gruenbacher
2005-02-27 15:22 ` [patch 01/16] acl kconfig cleanup Andreas Gruenbacher
2005-02-27 15:22 ` [patch 02/16] Qsort Andreas Gruenbacher
2005-02-27 15:22 ` [patch 03/16] Return -ENOSYS for RPC programs that are unavailable Andreas Gruenbacher
2005-02-27 15:22 ` [patch 04/16] Add missing -EOPNOTSUPP => NFS3ERR_NOTSUPP mapping in nfsd Andreas Gruenbacher
2005-02-27 15:22 ` [patch 05/16] Allow multiple programs to listen on the same port Andreas Gruenbacher
2005-02-27 15:22 ` [patch 06/16] Allow multiple programs to share the same transport Andreas Gruenbacher
2005-02-27 15:22 ` [patch 07/16] Lazy RPC receive buffer allocation Andreas Gruenbacher
2005-02-27 15:22 ` [patch 08/16] Encode and decode arbitrary XDR arrays Andreas Gruenbacher
2005-02-27 15:22 ` [patch 09/16] Add noacl nfs mount option Andreas Gruenbacher
2005-02-27 15:22 ` [patch 10/16] Infrastructure and server side of nfsacl Andreas Gruenbacher
2005-02-27 22:53 ` Christoph Hellwig
2005-02-27 15:22 ` [patch 11/16] Solaris nfsacl workaround Andreas Gruenbacher
2005-03-09 23:56 ` Trond Myklebust
2005-03-10 8:16 ` Andreas Gruenbacher [this message]
2005-02-27 15:22 ` [patch 12/16] nfs mknod cleanup Andreas Gruenbacher
2005-02-27 15:22 ` [patch 13/16] nfs mkdir cleanup Andreas Gruenbacher
2005-02-27 15:22 ` [patch 14/16] Client side of nfsacl Andreas Gruenbacher
2005-02-27 15:22 ` [patch 15/16] ACL umask handling workaround in nfs client Andreas Gruenbacher
2005-02-27 15:22 ` [patch 16/16] Cache acls on the nfs client side Andreas Gruenbacher
2005-02-27 16:35 ` [patch 00/16] NFSACL protocol extension for NFSv3 Andreas Gruenbacher
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=1110442616.25570.2.camel@winden.suse.de \
--to=agruen@suse.de \
--cc=Andries.Brouwer@cwi.nl \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
--cc=okir@suse.de \
--cc=trond.myklebust@fys.uio.no \
/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
Powered by JetHome