linux-kernel - Re: Linux 2.6.22 released

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]

Message-ID: <alpine.LFD.0.999.0707110002460.3412@woody.linux-foundation.org>
Date:	Wed, 11 Jul 2007 00:05:58 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Stefano Rivoir <s.rivoir@....it>
cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Linux 2.6.22 released

On Wed, 11 Jul 2007, Stefano Rivoir wrote:
> 
> Ok, the guilty bit is gcc: in my box, compiling kernel with gcc 4.2.x (which
> is installed on my debian/sid) turns into a hang (in init, seemingly, maybe
> not even in kernel itself), while gcc-4.1 is allright.
> 
> Probably it's something I had to know before... but the light lit when gcc
> crashed when compiling 2.6.22-git1...

Ok, I guess I should be happy, but gcc bugs end up being an absolute 
*horror* to try to debug, and there is always a slight possibility that it 
isn't a gcc bug, but some real kernel bug that is just hidden by the old 
code generation. It happens occasionally.

The fact that gcc itself crashed when trying to compile something does 
seem to indicate that it's one of those cases where it's unquestionably an 
outright gcc bug, and we don't have to worry about some dodgy kernel code. 
Which is a bit of a relief, but still, the gcc bug needs to be found, 
preferably before that thing actually gets released.

I'm hoping your Debian/sid gcc version is some very experimental 
known-buggy one, and not something that people _expect_ to be solid and 
work well?

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