From owner-freebsd-hackers  Thu Aug 12  1:49:26 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from not.demophon.com (ns.demophon.com [193.65.70.13])
	by hub.freebsd.org (Postfix) with ESMTP id 41EA514F6E
	for <hackers@freebsd.org>; Thu, 12 Aug 1999 01:49:19 -0700 (PDT)
	(envelope-from will@not.demophon.com)
Received: (from will@localhost)
	by not.demophon.com (8.9.3/8.8.7) id LAA59983;
	Thu, 12 Aug 1999 11:49:14 +0300 (EEST)
	(envelope-from will)
To: Matthew.Alton@anheuser-busch.com (Alton, Matthew)
Cc: hackers@freebsd.org
Subject: Re: BSD-XFS Update
References: <0740CBD1D149D31193EB0008C7C56836EB8B05@STLABCEXG012>
From: Ville-Pertti Keinonen <will@iki.fi>
Date: 12 Aug 1999 11:49:13 +0300
In-Reply-To: Matthew.Alton@anheuser-busch.com's message of "12 Aug 1999 00:49:21 +0300"
Message-ID: <86btcdmliu.fsf@not.demophon.com>
Lines: 15
X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald"
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


Matthew.Alton@anheuser-busch.com (Alton, Matthew) writes:

> I am currently researching methods for implementing the 64-bit
> syscalls stat64(), fstat64(), lseek64() &etc.  delineated in the
> SGI design doc _64 Bit File Access_  by Adam Sweeney.

Do the design docs indicate how inode numbers should interact with
userland APIs?

IIRC, inode numbers are 64-bit numbers in XFS.  Since ino_t, st_ino of
struct stat and d_fileno of struct dirent are only 32 bits, inode
numbers may be truncated and not appear unique to userland.  This
would break the assumptions of some code (e.g. getcwd(3), when not
using the kernel extension).


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message