linux-kernel - Re: [PATCH 02/21] afs: Fix const confusion in AFS

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:   Tue, 28 Nov 2017 08:50:50 -0800
From:   Andi Kleen <andi@...stfloor.org>
To:     David Howells <dhowells@...hat.com>
Cc:     Andi Kleen <andi@...stfloor.org>, linux-kernel@...r.kernel.org,
        x86@...nel.org, samitolvanen@...gle.com, alxmtvv@...il.com,
        linux-kbuild@...r.kernel.org, yamada.masahiro@...ionext.com,
        akpm@...ux-foundation.org, Andi Kleen <ak@...ux.intel.com>
Subject: Re: [PATCH 02/21] afs: Fix const confusion in AFS

On Tue, Nov 28, 2017 at 04:04:38PM +0000, David Howells wrote:
> Andi Kleen <andi@...stfloor.org> wrote:
> 
> > A trace point string cannot be const because the underlying special
> > section is not marked const. An LTO build complains about the
> > section attribute mismatch. Fix it by not marking the trace point
> > string in afs const.
> 
> Do you want this to go through my tree?

Yes please.

-Andi