All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	jeyu@redhat.com, Will Deacon <will.deacon@arm.com>,
	Rusty Russell <rusty@rustcorp.com.au>,
	Andrew Morton <akpm@linux-foundation.org>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	"paulus@samba.org" <paulus@samba.org>
Subject: Re: [PATCH v3 2/3] powerpc/reloc64: add support for 32-bit CRC pseudo-symbols
Date: Thu, 1 Dec 2016 16:28:32 +0000	[thread overview]
Message-ID: <CAKv+Gu_6hGpZA6G7cmvDG9R7dW3Yt_CebzwFfWzO1UebBOhk3Q@mail.gmail.com> (raw)
In-Reply-To: <CAKv+Gu_nPdQXxBnEYhYVt02SFbYx_bYtfU9LE8OkL5o0P5suOA@mail.gmail.com>

On 1 December 2016 at 09:45, Ard Biesheuvel <ard.biesheuvel@linaro.org> wrote:
> On 1 December 2016 at 09:39, Michael Ellerman <mpe@ellerman.id.au> wrote:
>> Ard Biesheuvel <ard.biesheuvel@linaro.org> writes:
>>> On 25 November 2016 at 11:29, Michael Ellerman <mpe@ellerman.id.au> wrote:
>>>> Ard Biesheuvel <ard.biesheuvel@linaro.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 ...

WARNING: multiple messages have this Message-ID (diff)
From: ard.biesheuvel@linaro.org (Ard Biesheuvel)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 2/3] powerpc/reloc64: add support for 32-bit CRC pseudo-symbols
Date: Thu, 1 Dec 2016 16:28:32 +0000	[thread overview]
Message-ID: <CAKv+Gu_6hGpZA6G7cmvDG9R7dW3Yt_CebzwFfWzO1UebBOhk3Q@mail.gmail.com> (raw)
In-Reply-To: <CAKv+Gu_nPdQXxBnEYhYVt02SFbYx_bYtfU9LE8OkL5o0P5suOA@mail.gmail.com>

On 1 December 2016 at 09:45, Ard Biesheuvel <ard.biesheuvel@linaro.org> wrote:
> On 1 December 2016 at 09:39, Michael Ellerman <mpe@ellerman.id.au> wrote:
>> Ard Biesheuvel <ard.biesheuvel@linaro.org> writes:
>>> On 25 November 2016 at 11:29, Michael Ellerman <mpe@ellerman.id.au> wrote:
>>>> Ard Biesheuvel <ard.biesheuvel@linaro.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 ...

  reply	other threads:[~2016-12-01 16:29 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-27 16:27 [PATCH v3 0/3] modversions: Fix CRC mangling under CONFIG_RELOCATABLE=y Ard Biesheuvel
2016-10-27 16:27 ` Ard Biesheuvel
2016-10-27 16:27 ` [PATCH v3 1/3] powerpc/reloc32: fix corrupted modversion CRCs Ard Biesheuvel
2016-10-27 16:27   ` Ard Biesheuvel
2016-10-28 10:27   ` Suzuki K Poulose
2016-10-28 10:27     ` Suzuki K Poulose
2016-10-27 16:27 ` [PATCH v3 2/3] powerpc/reloc64: add support for 32-bit CRC pseudo-symbols Ard Biesheuvel
2016-10-27 16:27   ` Ard Biesheuvel
2016-11-25 11:29   ` Michael Ellerman
2016-11-25 11:29     ` Michael Ellerman
2016-11-25 12:48     ` Ard Biesheuvel
2016-11-25 12:48       ` Ard Biesheuvel
2016-12-01  9:39       ` Michael Ellerman
2016-12-01  9:39         ` Michael Ellerman
2016-12-01  9:45         ` Ard Biesheuvel
2016-12-01  9:45           ` Ard Biesheuvel
2016-12-01 16:28           ` Ard Biesheuvel [this message]
2016-12-01 16:28             ` Ard Biesheuvel
2016-10-27 16:27 ` [PATCH v3 3/3] modversions: treat symbol CRCs as 32 bit quantities on 64 bit archs Ard Biesheuvel
2016-10-27 16:27   ` Ard Biesheuvel
2016-11-04  9:55 ` [PATCH v3 0/3] modversions: Fix CRC mangling under CONFIG_RELOCATABLE=y Ard Biesheuvel
2016-11-04  9:55   ` Ard Biesheuvel
2016-11-10  4:22   ` Michael Ellerman
2016-11-10  4:22     ` Michael Ellerman
2016-11-15  9:13     ` Ard Biesheuvel
2016-11-15  9:13       ` Ard Biesheuvel
2016-11-25  8:44       ` Ard Biesheuvel
2016-11-25  8:44         ` Ard Biesheuvel
2016-11-25 11:12         ` Michael Ellerman
2016-11-25 11:12           ` Michael Ellerman
2016-11-16 19:23 ` Uwe Kleine-König
2016-11-16 19:23   ` Uwe Kleine-König
2016-11-16 20:29   ` Ard Biesheuvel
2016-11-16 20:29     ` Ard Biesheuvel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAKv+Gu_6hGpZA6G7cmvDG9R7dW3Yt_CebzwFfWzO1UebBOhk3Q@mail.gmail.com \
    --to=ard.biesheuvel@linaro.org \
    --cc=akpm@linux-foundation.org \
    --cc=benh@kernel.crashing.org \
    --cc=jeyu@redhat.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpe@ellerman.id.au \
    --cc=paulus@samba.org \
    --cc=rusty@rustcorp.com.au \
    --cc=will.deacon@arm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.