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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 29 Sep 2006 14:40:46 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	john stultz <johnstul@...ibm.com>
Cc:	"K.R. Foley" <kr@...sft.com>, tglx@...utronix.de,
	linux-kernel@...r.kernel.org,
	"Paul E. McKenney" <paulmck@...ibm.com>,
	Dipankar Sarma <dipankar@...ibm.com>,
	Arjan van de Ven <arjan@...radead.org>,
	Andrew Morton <akpm@...l.org>
Subject: Re: 2.6.18-rt1


* john stultz <johnstul@...ibm.com> wrote:

> [snip]
> > c03879e8 r __ksymtab_find_next_bit
> > c03879f0 r __ksymtab_find_next_zero_bit
> > c03879f8 R __write_lock_failed
> > c0387a18 R __read_lock_failed
> > c0387a2c r __ksymtab___delay
> > c0387a34 r __ksymtab___const_udelay
> > c0387a3c r __ksymtab___udelay
> > c0387a44 r __ksymtab___ndelay
> > 
> > That __read/__write_lock_failed bit looks wrong.
> 
> 
> So it seems gcc 3.4.4 misplaces the __write_lock_failed function into 
> the ksymtab. It doesn't happen w/ 4.0.3.

i think it's an ld bug, and it's related to the nested 
.section/.previous use in the LOCK_PREFIX macro in 
include/asm-i386/alternatives.h.

this is the second time i have seen smp-alternatives related linker 
breakage.

	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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ