From: "J. Bruce Fields" <bfields@redhat.com>
To: Olga Kornievskaia <kolga@netapp.com>
Cc: linux-nfs <linux-nfs@vger.kernel.org>,
ng-linux-team <ng-linux-team@netapp.com>
Subject: Re: nfsd issue with a kerberized callback
Date: Tue, 17 Apr 2018 09:21:56 -0400 [thread overview]
Message-ID: <20180417132156.GA10291@parsley.fieldses.org> (raw)
In-Reply-To: <EC52DFFD-CB6F-45F5-BAB9-C684C205DE26@netapp.com>
On Mon, Apr 16, 2018 at 08:05:44PM -0400, Olga Kornievskaia wrote:
> > On Apr 16, 2018, at 5:29 PM, J. Bruce Fields <bfields@redhat.com> wrote:
> >> I believe what’s happening is that because the client hasn’t received
> >> CB_NULL that establishes a callback channel but got a CB_RECALL it’s
> >> just ignoring it.
> >
> > I see two succesful CB_NULL calls and replies, so I think the context
> > establishment worked. I don't know why there's a third CB_NULL in frame
> > 285.
>
> The two CB_NULL calls are both gss_init calls. They are not RPC NULL call. Server for some reason establishes 2 different gss context (again not necessarily a problem). The 3rd CB_NULL is gss_data and it sends an actual NULL call. I believe that’s the one that establishes a callback channel.
Oh, I see. No, that NULL call isn't necessary. It's just the server
probing to see whether the callback channel works. That NULL call isn't
required by the spec and everything should still work if the CB_RECALL
is sent out before it completes.
--b.
next prev parent reply other threads:[~2018-04-17 13:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-16 19:48 nfsd issue with a kerberized callback Olga Kornievskaia
2018-04-16 21:29 ` J. Bruce Fields
2018-04-17 13:08 ` Olga Kornievskaia
[not found] ` <EC52DFFD-CB6F-45F5-BAB9-C684C205DE26@netapp.com>
2018-04-17 13:21 ` J. Bruce Fields [this message]
2018-04-19 15:10 ` Olga Kornievskaia
2018-04-19 15:52 ` J. Bruce Fields
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=20180417132156.GA10291@parsley.fieldses.org \
--to=bfields@redhat.com \
--cc=kolga@netapp.com \
--cc=linux-nfs@vger.kernel.org \
--cc=ng-linux-team@netapp.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;
as well as URLs for NNTP newsgroup(s).