linux-kernel - Re: [linux-dvb] compiling on 2.6.28 broken?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 13 Jan 2009 11:37:00 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	handygewinnspiel@....de
Cc:	rjw@...k.pl, HWerner4@....de, viro@...iv.linux.org.uk,
	linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
	mchehab@...radead.org
Subject: Re: [linux-dvb] compiling on 2.6.28 broken?

On Tue, 13 Jan 2009 20:17:57 +0100 handygewinnspiel@....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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/