Re: [nfsv4] CREATE_SESSION backchannel question

"J. Bruce Fields" <bfields@fieldses.org> Thu, 14 October 2010 16:24 UTC

Return-Path: <bfields@fieldses.org>
X-Original-To: nfsv4@core3.amsl.com
Delivered-To: nfsv4@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D0FBD3A6A8B for <nfsv4@core3.amsl.com>; Thu, 14 Oct 2010 09:24:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.581
X-Spam-Level:
X-Spam-Status: No, score=-2.581 tagged_above=-999 required=5 tests=[AWL=0.018, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TN38JM+rn2II for <nfsv4@core3.amsl.com>; Thu, 14 Oct 2010 09:24:43 -0700 (PDT)
Received: from fieldses.org (fieldses.org [174.143.236.118]) by core3.amsl.com (Postfix) with ESMTP id 07A833A6A6E for <nfsv4@ietf.org>; Thu, 14 Oct 2010 09:24:43 -0700 (PDT)
Received: from bfields by fieldses.org with local (Exim 4.71) (envelope-from <bfields@fieldses.org>) id 1P6Qcz-0008Gd-UX; Thu, 14 Oct 2010 12:26:02 -0400
Date: Thu, 14 Oct 2010 12:26:01 -0400
To: "Matt W. Benjamin" <matt@linuxbox.com>
Message-ID: <20101014162601.GK24146@fieldses.org>
References: <916289894.7345.1287068685090.JavaMail.root@thunderbeast.private.linuxbox.com> <926671697.7347.1287068853883.JavaMail.root@thunderbeast.private.linuxbox.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <926671697.7347.1287068853883.JavaMail.root@thunderbeast.private.linuxbox.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
From: "J. Bruce Fields" <bfields@fieldses.org>
Cc: nfsv4 <nfsv4@ietf.org>
Subject: Re: [nfsv4] CREATE_SESSION backchannel question
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: NFSv4 Working Group <nfsv4.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/nfsv4>
List-Post: <mailto:nfsv4@ietf.org>
List-Help: <mailto:nfsv4-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Oct 2010 16:24:43 -0000

On Thu, Oct 14, 2010 at 11:07:33AM -0400, Matt W. Benjamin wrote:
> I wondered a bit about the server's backchannel preferences in
> CREATE_SESSION, for example, if the server implementation would prefer
> (or even require) a dedicated backchannel.  The server can accept or
> reject a client request to use the current connection as a forechannel
> and backchannel.

I'd never actually noticed that was allowed!

> If the server clears the backchannel flag, or the
> client did not set it, can the server expect that the client will
> offer a backchannel in a subsequent BIND_CONN_TO_SESSION (under its
> obligations under 2.9.2, item 3).

I don't think the existing Linux client is prepared to handle that; more
likely telling it that the backchannel wasn't set up will cause it to
destroy the client and try to create a new one, resulting in an infinite
loop....  (But I haven't tested that, much less other clients.)

It seems like mildly antisocial behavior on the part of the server, but
I can believe it would be convenient to not have to handle the
shared-connection case, and probably wouldn't be difficult to handle on
the client.

--b.