xfs
[Top] [All Lists]

Re: IA64 ino_t incorrectly sized?

To: Nathan Scott <nathans@xxxxxxx>
Subject: Re: IA64 ino_t incorrectly sized?
From: Jes Sorensen <jes@xxxxxxxxxxxxxxxxxx>
Date: 17 Sep 2003 10:33:47 -0400
Cc: linux-ia64@xxxxxxxxxxxxxxx, linux-xfs@xxxxxxxxxxx
In-reply-to: <20030917071045.GA3037@frodo>
References: <20030917071045.GA3037@frodo>
Sender: linux-xfs-bounce@xxxxxxxxxxx
User-agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7
>>>>> "Nathan" == Nathan Scott <nathans@xxxxxxx> writes:

Nathan> Does anyone know why the IA64 platform-specific ino_t
Nathan> definition is an int and not a long?  Patch below fixes this
Nathan> problem for me but I wonder if there will be side-effects I
Nathan> haven't considered (i.e. was there a reason for making this 32
Nathan> bits originally?).  If not, could the IA64 maintainers push
Nathan> this patch around to the official kernel trees for me?
Nathan> (pretty please)

Hi Nathan,

I am actually surprised it's still a 32 bit int in the kernel. I
deliberately used 64 bit types in glibc so it could be done
right. Must have slipped on fixing the kernel for this one.

David?

Cheers,
Jes


<Prev in Thread] Current Thread [Next in Thread>