From: Trond Myklebust <Trond.Myklebust@netapp.com>
To: Steve Dickson <steved@redhat.com>
Cc: Linux NFS Mailing list <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH 0/2] Enable the in-kernel id mapping to be on by default.
Date: Thu, 10 Nov 2011 15:52:22 -0500 [thread overview]
Message-ID: <1320958342.11956.22.camel@lade.trondhjem.org> (raw)
In-Reply-To: <1320956763-17935-1-git-send-email-steved@redhat.com>
On Thu, 2011-11-10 at 15:26 -0500, Steve Dickson wrote:
> This patch set enables the in-kernel id mapping upcall
> mechanism, which will fix deadlocks that can occur
> between the rpc.idmapd daemon and the kernel.
Which deadlocks are you thinking of?
> This set also correct the binary name in the kernel
> documentation
Note that we should also at some point change the default value of the
nfs4_disable_idmapping module parameter. Setting it to 'Y' so that the
NFS client starts by trying to use numeric u/gids with 'sec=sys' should
be safe, since we automatically fall back to using string-based
owner/group names if the server rejects numeric values.
Also note that older Linux servers return NFS4ERR_BADNAME in cases where
they should be using NFS4ERR_BADOWNER: please can distribution
maintainers make sure that they have applied commit
f6af99ec1b261e21219d5eba99e3af48fc6c32d4 (nfsd4: name->id mapping should
fail with BADOWNER not BADNAME).
Cheers
Trond
--
Trond Myklebust
Linux NFS client maintainer
NetApp
Trond.Myklebust@netapp.com
www.netapp.com
next prev parent reply other threads:[~2011-11-10 20:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-10 20:26 [PATCH 0/2] Enable the in-kernel id mapping to be on by default Steve Dickson
2011-11-10 20:26 ` [PATCH 1/2] Enable the in-kernel ID mapping upcall mechanism Steve Dickson
2011-11-10 20:26 ` [PATCH 2/2] idmapper.txt: Fix the upcall binary name Steve Dickson
2011-11-10 20:42 ` Bryan Schumaker
2011-11-10 20:52 ` Trond Myklebust [this message]
2011-11-10 21:32 ` [PATCH 0/2] Enable the in-kernel id mapping to be on by default Steve Dickson
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=1320958342.11956.22.camel@lade.trondhjem.org \
--to=trond.myklebust@netapp.com \
--cc=linux-nfs@vger.kernel.org \
--cc=steved@redhat.com \
/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