From owner-freebsd-fs@FreeBSD.ORG  Fri Aug  3 13:18:58 2007
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 8267416A418;
	Fri,  3 Aug 2007 13:18:58 +0000 (UTC)
	(envelope-from rees@citi.umich.edu)
Received: from citi.umich.edu (citi.umich.edu [141.211.133.111])
	by mx1.freebsd.org (Postfix) with ESMTP id 5732B13C442;
	Fri,  3 Aug 2007 13:18:58 +0000 (UTC)
	(envelope-from rees@citi.umich.edu)
Received: from citi.umich.edu (dsl093-001-248.det1.dsl.speakeasy.net
	[66.93.1.248])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(Client CN "Jim Rees", Issuer "CITI Production KCA" (verified OK))
	by citi.umich.edu (Postfix) with ESMTP id 6A9E446B1;
	Fri,  3 Aug 2007 09:18:57 -0400 (EDT)
Date: Fri, 3 Aug 2007 09:18:56 -0400
From: Jim Rees <rees@freebsd.org>
To: Eric Anderson <anderson@freebsd.org>
Message-ID: <20070803131855.GB32553@citi.umich.edu>
References: <46B31EA0.4010603@freebsd.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <46B31EA0.4010603@freebsd.org>
Cc: freebsd-fs@freebsd.org
Subject: Re: NFSv4 questions
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Aug 2007 13:18:58 -0000

The members of nfsv4_fattr don't have to exactly match the types in the
protocol.  The on-wire value is copied to the struct nfsv4_fattr by
nfsm_v4dissect_attrs_xx(), then to struct vattr by
nfs4_vnop_loadattrcache().  If the link count ever went above 2^16 there
would be a problem, but making fa4_nlink won't solve that.