linux-kernel - RE: [BUG]x86: relocatable doesn't work with new binutils

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: <9DA5872FEF993D41B7173F58FCF6BE940505136F@orsmsx504.amr.corp.intel.com>
Date:	Thu, 16 Dec 2010 20:54:38 -0800
From:	"Lu, Hongjiu" <hongjiu.lu@...el.com>
To:	"H. Peter Anvin" <hpa@...or.com>,
	"Li, Shaohua" <shaohua.li@...el.com>
CC:	lkml <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	"Huang, Ying" <ying.huang@...el.com>
Subject: RE: [BUG]x86: relocatable doesn't work with new binutils

I just released the Linux binutils 2.21.51.0.4:

http://gcc.gnu.org/ml/gcc/2010-12/msg00397.html


H.J.


> -----Original Message-----
> From: H. Peter Anvin [mailto:hpa@...or.com]
> Sent: Thursday, December 16, 2010 7:25 PM
> To: Li, Shaohua
> Cc: lkml; Andrew Morton; Lu, Hongjiu; Huang, Ying
> Subject: Re: [BUG]x86: relocatable doesn't work with new binutils
> 
> On 12/16/2010 07:21 PM, Shaohua Li wrote:
> > On Fri, 2010-12-17 at 10:59 +0800, H. Peter Anvin wrote:
> >> On 12/16/2010 06:42 PM, Shaohua Li wrote:
> >>> We can easily workaround this issue by moving jiffies to a section
> or at
> >>> least warn people if such binutils are using. what should we do?
> >>
> >> I think we should do the workaround, but still get distros to
> update the
> >> broken binutils.
> > Here is my workaround.
> > The problem is a lot of kernel versions are affected by this, fix
> all?
> 
> I suspect the stable kernels should be able to take the patch easily
> enough.
> 
> 	-hpa
> 
> 
> --
> H. Peter Anvin, Intel Open Source Technology Center
> I work for Intel.  I don't speak on their behalf.