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:	Wed, 14 Jan 2009 13:29:10 -0500
From:	Chris Mason <chris.mason@...cle.com>
To:	Matthew Wilcox <matthew@....cx>
Cc:	Andrew Morton <akpm@...ux-foundation.org>, handygewinnspiel@....de,
	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, 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



--
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/