IETF Logo Mail Archive

Re: [nfsv4] Fw: New Version Notification for draft-naik-nfsv4-xattrs-02.txt

Christoph Hellwig <hch@lst.de> Mon, 06 July 2015 09:14 UTC

Return-Path: <hch@lst.de>
X-Original-To: nfsv4@ietfa.amsl.com
Delivered-To: nfsv4@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B8FC1A9142 for <nfsv4@ietfa.amsl.com>; Mon, 6 Jul 2015 02:14:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.339
X-Spam-Level:
X-Spam-Status: No, score=0.339 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, HELO_EQ_DE=0.35, T_RP_MATCHES_RCVD=-0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tVdE0GSLZJGn for <nfsv4@ietfa.amsl.com>; Mon, 6 Jul 2015 02:14:38 -0700 (PDT)
Received: from newverein.lst.de (verein.lst.de [213.95.11.211]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7BBC91A9134 for <nfsv4@ietf.org>; Mon, 6 Jul 2015 02:14:38 -0700 (PDT)
Received: by newverein.lst.de (Postfix, from userid 2407) id 664DF691F7; Mon, 6 Jul 2015 11:14:36 +0200 (CEST)
Date: Mon, 06 Jul 2015 11:14:36 +0200
From: Christoph Hellwig <hch@lst.de>
To: Manoj Naik <mnaik@us.ibm.com>
Message-ID: <20150706091436.GA7082@lst.de>
References: <201507060259.t662xWrC001614@d03av01.boulder.ibm.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <201507060259.t662xWrC001614@d03av01.boulder.ibm.com>
User-Agent: Mutt/1.5.17 (2007-11-01)
Archived-At: <http://mailarchive.ietf.org/arch/msg/nfsv4/Szr60XxchS7h6a7WjbHcR1Jt6MM>
Cc: "nfsv4 list (nfsv4@ietf.org)" <nfsv4@ietf.org>
Subject: Re: [nfsv4] Fw: New Version Notification for draft-naik-nfsv4-xattrs-02.txt
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: NFSv4 Working Group <nfsv4.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Mon, 06 Jul 2015 09:14:40 -0000

On Sun, Jul 05, 2015 at 07:58:35PM -0700, Manoj Naik wrote:
> I have just submitted a new revision of the xattr draft. Changes include:
> - Add new operations to list/remove; simplify get/set

Thanks, from a quick glance the operations look sensible now.

> - Remove restrictions on total size, max size

So how do we handle the cases where the client tries to set an xattr
size, total size or key lenghth that exceeds the servers limit?  We should
define specific error codes for these cases at least.  I also thing
attrs might still be useful, even if some syscall interface currently
can't support those.

v2.23.0 | Report a Bug | By Email