linux-kernel - Re: [PATCH v3 2/3] powerpc/reloc64: add support for 32-bit CRC pseudo-symbols

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: <874m2ooumq.fsf@concordia.ellerman.id.au>
Date:   Thu, 01 Dec 2016 20:39:57 +1100
From:   Michael Ellerman <mpe@...erman.id.au>
To:     Ard Biesheuvel <ard.biesheuvel@...aro.org>
Cc:     "linux-kernel\@vger.kernel.org" <linux-kernel@...r.kernel.org>,
        "linux-arm-kernel\@lists.infradead.org" 
        <linux-arm-kernel@...ts.infradead.org>, jeyu@...hat.com,
        Will Deacon <will.deacon@....com>,
        Rusty Russell <rusty@...tcorp.com.au>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Benjamin Herrenschmidt <benh@...nel.crashing.org>,
        "paulus\@samba.org" <paulus@...ba.org>
Subject: Re: [PATCH v3 2/3] powerpc/reloc64: add support for 32-bit CRC pseudo-symbols

Ard Biesheuvel <ard.biesheuvel@...aro.org> writes:
> On 25 November 2016 at 11:29, Michael Ellerman <mpe@...erman.id.au> wrote:
>> Ard Biesheuvel <ard.biesheuvel@...aro.org> writes:
>>
>> [    7.607687] kvm: disagrees about version of symbol module_layout
>> [    7.846799] virtio: disagrees about version of symbol module_layout
>> [   22.012615] crc32c_vpmsum: disagrees about version of symbol module_layout
>> [   22.012959] libcrc32c: disagrees about version of symbol module_layout
>>
>
> Sigh. I suppose your modversions fixes are queued for v4.10? It's
> probably best to revisit this after the v4.10 merge window closes
> then, just to make sure I'm not aiming for a moving target.

Actually they were merged into 4.9-rc7 ish.

But I'm still seeing the same as above with this series rebased on top
of that, and I'm a bit short on time to debug it ATM.

So during the 4.10 cycle is probably the best we can hope for, sorry.

cheers