linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tigran Mkrtchyan <tigran.mkrtchyan@desy.de>
To: NFS list <linux-nfs@vger.kernel.org>
Subject: missing verifier in rpcsec_gss calls
Date: Tue, 21 Jun 2011 10:17:07 +0200	[thread overview]
Message-ID: <4E005383.6030206@desy.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 412 bytes --]

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

Regards,
    Tigran.

[-- Attachment #2: mount-krb5i.dump --]
[-- Type: application/octet-stream, Size: 3312 bytes --]

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

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-21  8:17 Tigran Mkrtchyan [this message]
2011-06-21 17:56 ` missing verifier in rpcsec_gss calls J. Bruce Fields
  -- 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=4E005383.6030206@desy.de \
    --to=tigran.mkrtchyan@desy.de \
    --cc=linux-nfs@vger.kernel.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).