linux-kernel - Re: [tip:x86/urgent] x86: Fix build with older binutils andconsolidate linker script

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: <20090825141405.GA14879@elte.hu>
Date:	Tue, 25 Aug 2009 16:14:05 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Jan Beulich <JBeulich@...ell.com>
Cc:	tglx@...utronix.de, mingo@...hat.com, linux-kernel@...r.kernel.org,
	linux-tip-commits@...r.kernel.org, hpa@...or.com
Subject: Re: [tip:x86/urgent] x86: Fix build with older binutils
	andconsolidate linker script


* Jan Beulich <JBeulich@...ell.com> wrote:

> >>> Ingo Molnar <mingo@...e.hu> 25.08.09 15:56 >>>
> >* Jan Beulich <JBeulich@...ell.com> wrote:
> >> Sorry for having forgotten to do so before submitting the first 
> >> time (I know I had intended to).
> >
> >This happens. I'm still unsure whether we can do it in .31.0 or need 
> >to delay it to .31.1 via a -stable backport tag. One more problem 
> >with it and i think we'll need to delay it - it's just too large and 
> >changes too many aspects of the linker script.
> >
> >Would it be possible to split it into two pieces: 'minimal fix' and 
> >'clean up' portions?
> 
> Besides being cumbersome, that would make it even larger, so I'd 
> say that's not worth it.

I mean the two patches yield the same end result. The first one 
(which is smaller, hopefully) gets committed to x86/urgent, the 
second one (the cleanups and other non-essentials) gets pushed 
upstream in .32.

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