From: Jeff Layton Subject: Re: [PATCH] make last_inode counter in new_inode 32-bit on kernels that offer x86 compatability Date: Mon, 06 Nov 2006 13:31:14 -0500 Message-ID: <1162837874.12129.1.camel@dantu.rdu.redhat.com> References: <1162836725.6952.28.camel@dantu.rdu.redhat.com> <20061106182222.GO27140@parisc-linux.org> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org Return-path: To: Matthew Wilcox In-Reply-To: <20061106182222.GO27140@parisc-linux.org> Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Mon, 2006-11-06 at 11:22 -0700, Matthew Wilcox wrote: > On Mon, Nov 06, 2006 at 01:12:05PM -0500, Jeff Layton wrote: > > The attached patch remedies this by making the last_inode counter be an > > unsigned int on kernels that have ia32 compatability mode enabled. > > ... and this only happens on ia64/x86_64 kernels, not sparc64, ppc64, > s390x, parisc64 or mips64? > Yeah, that was my big question. I'd only seen this on ia32 compatability modes, but clearly its a problem where unsigned long is a different size between a 64-bit kernel and its 32-bit compatability mode. I'll have a look at CONFIG_COMPAT and likely respin. Thanks, Jeff