On Tue, 2010-11-30 at 10:36 -0500, Steve Dickson wrote: > > On 11/29/2010 02:09 PM, Trond Myklebust wrote: > > On Mon, 2010-11-29 at 14:01 -0500, J. Bruce Fields wrote: > >> On Mon, Nov 29, 2010 at 07:38:30PM +0100, Spelic wrote: > >>> On 11/29/2010 07:22 PM, Trond Myklebust wrote: > >>>> On Mon, 2010-11-29 at 19:12 +0100, Spelic wrote: > >>>> No. That is not allowed by the spec. > >>>> > >>>> Trond > >>> > >>> Too bad!! :-(( > >>> Was that spec decision really wise? :-/ > >>> > >>> > >>> BTW: > >>> I've just noticed two discussions dated a few months ago in this ML > >>> regarding this. > >>> the thread named 'numeric UIDs' > >> > >> There's also a reference to the spec language there--we'd be violating a > >> "SHOULD", but I think it would be acceptable if it smooths the v3->v4 > >> upgrade path for users in your situation. > >> > >> I think steved's changes still need to be ported to libnfsidmap? > > > > I don't see how steved's changes will fix this problem. If the client > > has a mapping, it will (MUST) send the mapped uid/gid and the server > > still has to make sense of that. Ditto if the server has a mapping, and > > the client does not. > I actually thought it did... How? The userland library has no concept of whether or not the server accepts unmapped uids and gids. > Now that the libnfsidmap maintainership has been handed over to me > and I'm about to enable the new nfsidmapper when I commit the > "libnfsidmap: Add numerical string translation" patch... Its > probably time I take a second look at those patches to see > if we can ease some of this pain... Some reasons for doing this in the kernel are: 1) it is easy to do so. 2) it allows the kernel to take action to recover 3) it fixes the nfsroot problem, provided that the server also sends uids/gids in this situation. -- Trond Myklebust Linux NFS client maintainer NetApp Trond.Myklebust@xxxxxxxxxx www.netapp.com -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
