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: <5398749B.4090209@zytor.com>
Date:	Wed, 11 Jun 2014 08:24:11 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Andy Lutomirski <luto@...capital.net>,
	Josh Boyer <jwboyer@...oraproject.org>
CC:	"Linux-Kernel@...r. Kernel. Org" <linux-kernel@...r.kernel.org>
Subject: Re: vdso_install target broken post-3.15

On 06/11/2014 08:20 AM, Andy Lutomirski wrote:
> 
> Is vdso_install supposed to install a .so file or just a .so.dbg file?
>  I'm having trouble parsing this:
> 
> quiet_cmd_vdso_install = INSTALL $@
>       cmd_vdso_install = cp $(obj)/$@...g $(MODLIB)/vdso/$@
> $(vdso-install-y): %.so: $(obj)/%.so.dbg FORCE
>         @mkdir -p $(MODLIB)/vdso
>         $(call cmd,vdso_install)
> 
> This seems like a rather complicated way of saying that the .so.dbg is
> installed with the .dbg at the end removed.  We can do that.  Let me
> see if I can disentangle the makefile enough.
> 

That is, indeed, what it says.

> If we need real stripped .so files, vdso2c knows how to generate them,
> but the makefile doesn't invoke it like that.  I don't see why we'd
> want to install them, though.

I don't think there is any point in that.

	-hpa

--
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