linux-kernel - Re: [git pull] x86 fixes

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: <499FBE67.7080601@zytor.com>
Date:	Sat, 21 Feb 2009 00:42:15 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Ingo Molnar <mingo@...e.hu>
CC:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Sam Ravnborg <sam@...nborg.org>, linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [git pull] x86 fixes

Ingo Molnar wrote:
> * Ingo Molnar <mingo@...e.hu> wrote:
> 
>> | commit fa2144ba9a31d1d0dc9607508576c3850e0d95b1
>> | Author: Sam Ravnborg <sam@...nborg.org>
>> | Date:   Fri Feb 15 13:53:11 2008 +0100
>> |
>> |     kbuild: explain why DEBUG_SECTION_MISMATCH is UNDEFINED
> 
> hm, that's 2008 not 2009.
> 
> I dont know why the section warnings went away, but i frequently 
> saw these warnings and i never forced 
> CONFIG_DEBUG_SECTION_MISMATCH on the command line.
> 

Either way, I was rather unhappy to find out that my test scripts were
silently broken by this change a year ago.  Furthermore, right now there
are only 9 section warnings in allyesconfig on x86-64 and 12 on i386,
and one of those was the one I just corrected.  The last thing we need
is them to be squelshed.

These patches should be backed out at once.

	-hpa

-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.

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