From: "Brian J. Murrell" <brian@interlinx.bc.ca>
To: linux-nfs@vger.kernel.org
Cc: Kevin Coffman <public-kwc-vtMw8L3fJ9vSiEDVxGk4TQ@lo.gmane.org>
Subject: Re: different kernels mean NFS4/GSSAPI works or doesn't
Date: Sat, 26 Mar 2011 20:07:12 -0400 [thread overview]
Message-ID: <4D8E7FB0.9060109@interlinx.bc.ca> (raw)
In-Reply-To: <1300900035.11677.12.camel@lade.trondhjem.org>
[-- Attachment #1: Type: text/plain, Size: 1448 bytes --]
On 11-03-23 01:07 PM, Trond Myklebust wrote:
> Please don't remove people from the Cc list.
Fair enough. Personally, I dislike getting two copies, but I can
respect others' wishes.
> You said this happens only with RPCSEC_GSS?
Indeed. Hrm. Well, to be honest my two scenarios are NFS4 with
RPCSEC_GSS and NFSv3. I've never really looked into NFS4 without
RPCSEC_GSS. Is that even possible? What's the point? I guess there
are protocol improvements in NFS4 aside from RPCSEC_GSS?
> Have you tried bisecting, to see which changes caused it?
I just did, using Ubuntu's "mainline" kernels, which AFAIU are upstream
kernel source without any of their special sauce, but built with their
.configs.
It seems the problem was introduced in 2.6.32.12. I don't really know
which commit between 2.6.32.11 and 2.6.32.12 though. In fact I don't
even know where to find these so-called .11 and .12 4th order of
releases to see what all went into it.
I did find
http://www.kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.32.11 but a
gitweb interface to the changes would be much more useful I think.
Although the number of changes that show up there for matches of /nfs/
or /gss/ are quite small (only one for the latter).
> You can
> probably restrict yourself to bisecting changes to include/linux/sunrpc,
> net/sunrpc and net/sunrpc/auth_gss.
If I could find a gitweb tree to grovel through. :-)
b.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2011-03-27 0:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-22 23:27 different kernels mean NFS4/GSSAPI works or doesn't Brian J. Murrell
2011-03-23 2:41 ` Kevin Coffman
2011-03-23 11:03 ` Brian J. Murrell
2011-03-23 14:29 ` Kevin Coffman
[not found] ` <AANLkTi=b1z0MrYYQmidbra0EHanegcLO5qoOScLq21rb-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-03-23 15:07 ` Brian J. Murrell
2011-03-23 17:07 ` Trond Myklebust
2011-03-27 0:07 ` Brian J. Murrell [this message]
[not found] ` <1300900035.11677.12.camel-SyLVLa/KEI9HwK5hSS5vWB2eb7JE58TQ@public.gmane.org>
2011-03-27 12:42 ` Brian J. Murrell
2011-03-30 12:09 ` Brian J. Murrell
2011-04-01 13:02 ` Brian J. Murrell
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=4D8E7FB0.9060109@interlinx.bc.ca \
--to=brian@interlinx.bc.ca \
--cc=linux-nfs@vger.kernel.org \
--cc=public-kwc-vtMw8L3fJ9vSiEDVxGk4TQ@lo.gmane.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;
as well as URLs for NNTP newsgroup(s).