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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAKv+Gu_6hGpZA6G7cmvDG9R7dW3Yt_CebzwFfWzO1UebBOhk3Q@mail.gmail.com>
Date:   Thu, 1 Dec 2016 16:28:32 +0000
From:   Ard Biesheuvel <ard.biesheuvel@...aro.org>
To:     Michael Ellerman <mpe@...erman.id.au>
Cc:     "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "linux-arm-kernel@...ts.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@...ba.org" <paulus@...ba.org>
Subject: Re: [PATCH v3 2/3] powerpc/reloc64: add support for 32-bit CRC pseudo-symbols

On 1 December 2016 at 09:45, Ard Biesheuvel <ard.biesheuvel@...aro.org> wrote:
> On 1 December 2016 at 09:39, Michael Ellerman <mpe@...erman.id.au> wrote:
>> 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.
>>
>
> Not a problem. The only question is whether 1/3 of this series fixes
> an actual bug or not, given that the CONFIG_RELOCATABLE workaround has
> been made ppc64 only.
>
> But for the remaining patches, I'm happy to respin after the v4.10
> merge window closes, and get something queued for v4.11
>

Actually, given the uncertain fate of modversions in general, we may
no longer have to bother by the time the v4.11 merge window opens ...