linux-kernel - Re: [PATCH] fix UML on x86-64

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.1.10.0805061625090.32269@woody.linux-foundation.org>
Date:	Tue, 6 May 2008 16:27:27 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Ulrich Drepper <drepper@...hat.com>
cc:	linux-kernel@...r.kernel.org,
	user-mode-linux-devel@...ts.sourceforge.net,
	akpm@...ux-foundation.org, mingo@...e.hu, tglx@...utronix.de
Subject: Re: [PATCH] fix UML on x86-64



On Tue, 6 May 2008, Ulrich Drepper wrote:
>
> This patch breaks UML for me on x86-64 running Fedora 8 (gcc 4.1.2):

It breaks things how?

Because on x86, the cut-off is gcc4 vs pre-4. See arch/x86/Makefile:

        KBUILD_CFLAGS += $(shell if [ $(call cc-version) -lt 0400 ] ; then \
                echo $(call cc-option,-fno-unit-at-a-time); fi ;)

and it's a bit distressing that these compiler flags are set two different 
ways (in fact, I was already bothered by the fact that UML sets it totally 
independently of x86 in the first place).

So what is the UML failure behaviour with gcc-4.1.2?

			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/