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@xxxxxxxxxx> 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. -- 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
