linux-kernel - Re: REGRESSION: x86 vDSO: remove vdso-syms.o

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: <20080211231635.GA27673@elte.hu>
Date:	Tue, 12 Feb 2008 00:16:35 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Roland McGrath <roland@...hat.com>
Cc:	Priit Laes <plaes@...es.org>, linux-kernel@...r.kernel.org,
	Thomas Gleixner <tglx@...utronix.de>,
	Sam Ravnborg <sam@...nborg.org>
Subject: Re: REGRESSION: x86 vDSO: remove vdso-syms.o


* Roland McGrath <roland@...hat.com> wrote:

> I was not able to reproduce this failure.  Those symbols should be 
> defined by arch/x86/vdso/vdso-syms.lds, a file generated by the build.  
> If that file is empty in your build, remove it and see if it gets 
> regenerated properly, or try a clean build.  If the problem persists, 
> please send me your complete .config file.

if that file is empty, it might be the effect of a Ctrl-C. I sometimes 
get that on .o files, if i Ctrl-C a highly parallel make -j at the wrong 
moment. (is this expected behavior? It's been like this for a long 
time.)

	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/