linux-kernel - Re: [PATCH] Fix multiple definition error under lto

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] [day] [month] [year] [list]

Message-ID: <alpine.LRH.2.00.1612131534510.8802@gjva.wvxbf.pm>
Date:   Tue, 13 Dec 2016 15:36:57 +0100 (CET)
From:   Jiri Kosina <jikos@...nel.org>
To:     Eduardo Valentin <edubezval@...il.com>
cc:     Zhang Rui <rui.zhang@...el.com>,
        Peter Foley <pefoley2@...oley.com>,
        linux-kernel@...r.kernel.org, linux-pm@...r.kernel.org
Subject: Re: [PATCH] Fix multiple definition error under lto

On Mon, 12 Dec 2016, Eduardo Valentin wrote:

> > > drivers/thermal/built-in.o: In function `type_show.lto_priv.33':
> > > (.text+0x3d80): multiple definition of `type_show.lto_priv.33'
> > > drivers/base/built-in.o:(.text+0x2a40): first defined here
> > > 
> > can you illustrate how to reproduce this problem?
> 
> same here. I am not able to see this. Can you please describe your
> environment?

I'm pretty sure he's experimenting with LTO and hitting the LTO phase 
getting link-time symbol conflicts between definitions coming from thermal 
and base. I'd even say this to be a toolchain bug, given the fact that 
both symbols are static.

-- 
Jiri Kosina
SUSE Labs