From: Randy Dunlap <rdunlap@infradead.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Build regressions/improvements in v5.17-rc4
Date: Wed, 16 Feb 2022 08:52:15 -0800 [thread overview]
Message-ID: <0ddaa732-4112-0e3e-e395-bc92af2a194f@infradead.org> (raw)
In-Reply-To: <CAMuHMdW9Po1V5yH+gHzUJGx8NLcoCUyBa4FF41eH9vDbQWBW8w@mail.gmail.com>
On 2/16/22 00:05, Geert Uytterhoeven wrote:
> Hi Randy,
>
> On Tue, Feb 15, 2022 at 10:14 PM Randy Dunlap <rdunlap@infradead.org> wrote:
>> On 2/14/22 01:37, Geert Uytterhoeven wrote:
>>> Below is the list of build error/warning regressions/improvements in
>>> v5.17-rc4[1] compared to v5.16[2].
>>>
>>> Summarized:
>>> - build errors: +14/-2
>>> - build warnings: +23/-25
>
>>> 23 warning regressions:
>>> + modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qed/qed.o(.data+0x14410): Section mismatch in reference from the variable qed_mfw_legacy_maps to the variable .init.rodata:qed_mfw_legacy_bb_100g: => N/A
>>
>> This is a little confusing. Was there a problem with qed and qede network drivers?
>> Is it still a problem?
>
> Yes there is.
>
>> Many of the lines above and below are very similar.
>
> Sorry, my script to filter out errors/warnings that just moved does
> not handle modpost output yet.
I see. No problem.
>> If there is still a problem, what $ARCH and config(s) cause it?
>> I can't reproduce it on 11 $ARCH tries.
>> Or maybe it is compiler-specific also.
>
> xtensa-gcc11/xtensa-allmodconfig
> http://kisskb.ellerman.id.au/kisskb/buildresult/14697521/
> I don't know why it doesn't show up in the other gcc11 builds.
>
> I had a look at the problem before, but fixing it is non-trivial:
> the driver uses a non-init table of structures that contains pointers
> to init data (only used early) and non-init data (used later, too).
> Sprinkling __ref over the code may help, but won't protect against
> introducing new bugs.
Got it. Thanks again.
--
~Randy
prev parent reply other threads:[~2022-02-16 16:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-14 9:37 Geert Uytterhoeven
2022-02-14 10:02 ` Geert Uytterhoeven
2022-02-15 21:13 ` Randy Dunlap
2022-02-16 8:05 ` Geert Uytterhoeven
2022-02-16 16:52 ` Randy Dunlap [this message]
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=0ddaa732-4112-0e3e-e395-bc92af2a194f@infradead.org \
--to=rdunlap@infradead.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®