Date: Tue, 13 Jan 2009 11:37:00 -0800
From: Andrew Morton <akpm@linux-foundation.org>
To: handygewinnspiel@gmx.de
Cc: rjw@sisk.pl, HWerner4@gmx.de, viro@zeniv.linux.org.uk,
       linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
       mchehab@infradead.org
Subject: Re: [linux-dvb] compiling on 2.6.28 broken?
Message-Id: <20090113113700.776a94b5.akpm@linux-foundation.org>
In-Reply-To: <20090113191757.74290@gmx.net>
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>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 918
Lines: 26

On Tue, 13 Jan 2009 20:17:57 +0100 handygewinnspiel@gmx.de wrote:

> > 
> > It's the first such report I've seen.
> > 
> > Could you please generate the strace output for the failing command so
> > we can see which syscall is failing?
> 
> Attached two strace logs, one for the failed version, one for the working version.
> 

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?

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/