linux-kernel - Re: What was in the x86 merge for .20

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]

Date:	Fri, 8 Dec 2006 14:51:07 +0200
From:	Muli Ben-Yehuda <muli@...ibm.com>
To:	Arkadiusz Miskiewicz <arekm@...en.pl>
Cc:	Andi Kleen <ak@...e.de>, linux-kernel@...r.kernel.org
Subject: Re: What was in the x86 merge for .20

On Fri, Dec 08, 2006 at 01:04:23PM +0100, Arkadiusz Miskiewicz wrote:
> On Friday 08 December 2006 04:01, Andi Kleen wrote:
> 
> > - Support for a Processor Data Area (PDA) on i386. This makes
> > the code more similar to x86-64 and will allow some other
> > optimizations in the future.
> 
>   LD      .tmp_vmlinux1
> arch/i386/kernel/built-in.o: In function `math_emulate':
> (.text+0x3809): undefined reference to `_proxy_pda'
> arch/i386/kernel/built-in.o: In function `smp_apic_timer_interrupt':
> (.text+0xe140): undefined reference to `_proxy_pda'
> kernel/built-in.o: In function `sys_set_tid_address':
> (.text+0x370b): undefined reference to `_proxy_pda'
> kernel/built-in.o: In function `switch_uid':
> (.text+0xcc6c): undefined reference to `_proxy_pda'
> mm/built-in.o: In function `sys_munlock':
> (.text+0xcaf1): undefined reference to `_proxy_pda'
> mm/built-in.o:(.text+0xcc11): more undefined references to `_proxy_pda' follow
> make: *** [.tmp_vmlinux1] Błąd 1
> 
> Something related (git tree fetched 1-2h ago) ?

Probably. Please send your .config.

Cheers,
Muli
-
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/