All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Tigran Mkrtchyan <tigran.mkrtchyan@desy.de>
Cc: NFS list <linux-nfs@vger.kernel.org>
Subject: Re: missing verifier in rpcsec_gss calls
Date: Tue, 21 Jun 2011 13:56:55 -0400	[thread overview]
Message-ID: <20110621175655.GA26923@fieldses.org> (raw)
In-Reply-To: <4E005383.6030206@desy.de>

On Tue, Jun 21, 2011 at 10:17:07AM +0200, Tigran Mkrtchyan wrote:
> this is what I am observing with v4.0 and v4.1.
> sometimes, mostly on RPCSEC_GSS_DESTROY,
> in the PC calls missing verifier. This is against my
> server and linux server.
> 
> Packets attached. Please have a look at the packet 15.
> 100% reproducible.
> 
> 
> I tried vanilla 2.6.39 and 3.0.0-rc3 from
> git://linux-nfs.org/~trondmy/nfs-2.6.git
>    9cff1ffd4d477f541d5644f0ec25ee40025fa806 origin/linux-next

Looking at the code quickly:

The only place I see gss headers encoded is in gss_marshal(), which
unconditionally encodes the verifier.

So the length must be getting messed up after that?

I don't see it....

--b.

  reply	other threads:[~2011-06-21 17:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-21  8:17 missing verifier in rpcsec_gss calls Tigran Mkrtchyan
2011-06-21 17:56 ` J. Bruce Fields [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-06-20 14:09 Tigran Mkrtchyan

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=20110621175655.GA26923@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=tigran.mkrtchyan@desy.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.