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: <20080212003631.BF1D8270191@magilla.localdomain>
Date:	Mon, 11 Feb 2008 16:36:31 -0800 (PST)
From:	Roland McGrath <roland@...hat.com>
To:	Priit Laes <plaes@...es.org>
Cc:	linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...e.hu>
Subject: Re: REGRESSION: x86 vDSO: remove vdso-syms.o

I did not see it with your .config either.

> This fails with clean build. And vdso-syms.lds is not empty.
> 
> Contents of ?arch/x86/vdso/vdso-syms.lds:
> VDSO64_PRELINK = 0xffffffffff700000;
> VDSO64_jiffies = 0xffffffffff7004b8;

Odd.  The missing symbols come from the same place that VDSO64_jiffies did.
The end of the arch/x86/vdso/vdso.lds file in your build should have these:

VDSO64_jiffies = vdso_jiffies;
VDSO64_vgetcpu_mode = vdso_vgetcpu_mode;
VDSO64_vsyscall_gtod_data = vdso_vsyscall_gtod_data;

readelf -s arch/x86/vdso/vvar.o in your build should show (among others):

     8: 0000000000000000     8 OBJECT  GLOBAL DEFAULT    4 vdso_jiffies
     9: 0000000000000008     8 OBJECT  GLOBAL DEFAULT    4 vdso_vgetcpu_mode
    10: 0000000000000010     8 OBJECT  GLOBAL DEFAULT    4 vdso_vsyscall_gtod_data

If either of those is not all there, you'll have to look into what's
happening in the generation of the respective files.


Thanks,
Roland
--
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/