From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Mason Subject: Re: [linux-dvb] compiling on 2.6.28 broken? Date: Wed, 14 Jan 2009 13:29:10 -0500 Message-ID: <1231957750.8269.28.camel@think.oraclecorp.com> References: <20090112190420.51f75853@pedra.chehab.org> <20090112132130.6c932b85.akpm@linux-foundation.org> <20090112220624.4fbfee34@pedra.chehab.org> <20090112162337.318dd61d.akpm@linux-foundation.org> <20090113184755.87720@gmx.net> <20090113105947.9e774b69.akpm@linux-foundation.org> <20090113191757.74290@gmx.net> <20090113113700.776a94b5.akpm@linux-foundation.org> <20090113203843.GJ29283@parisc-linux.org> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Cc: Andrew Morton , handygewinnspiel@gmx.de, rjw@sisk.pl, HWerner4@gmx.de, viro@zeniv.linux.org.uk, linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, mchehab@infradead.org To: Matthew Wilcox Return-path: Received: from rcsinet12.oracle.com ([148.87.113.124]:53339 "EHLO rgminet12.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753391AbZANSai (ORCPT ); Wed, 14 Jan 2009 13:30:38 -0500 In-Reply-To: <20090113203843.GJ29283@parisc-linux.org> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Tue, 2009-01-13 at 13:38 -0700, Matthew Wilcox wrote: > On Tue, Jan 13, 2009 at 11:37:00AM -0800, Andrew Morton wrote: > > I'd have expected to see stat() returning -EOVERFLOW, but it isn't there. > > > > googling around a bit seems to indcate that this might be a glibc issue: > > > > http://sourceware.org/bugzilla/show_bug.cgi?id=1864 > > http://bugs.gentoo.org/show_bug.cgi?id=146951 > > > > But the traces are all using stat64() and fstat64(). And why would it > > just start occurring now? > > Maybe glibc is using the 64-bit stat calls and returning -EOVERFLOW to > the application when the results from the kernel turn out to be > 32-bit > in size? > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=6c31b93a14a453c8756ffd228e24910ffdf30c5d I'd guess the commit above is related, although I don't see any way for it to make things interesting without the user doing mount -o inode64. strace -v should show us more, it would show if the inode numbers coming out of stat64 are big. -chris