linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Russell King <rmk+kernel@armlinux.org.uk>,
	Masahiro Yamada <masahiroy@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Miguel Ojeda <ojeda@kernel.org>
Subject: Re: Linux 6.1-rc3
Date: Tue, 1 Nov 2022 11:26:16 -0700	[thread overview]
Message-ID: <20221101182616.GA1328619@roeck-us.net> (raw)
In-Reply-To: <29d07648-29a9-432a-a666-f9c9e55c32f6@app.fastmail.com>

On Tue, Nov 01, 2022 at 06:57:41PM +0100, Arnd Bergmann wrote:
> On Tue, Nov 1, 2022, at 18:29, Linus Torvalds wrote:
> 
> > IOW, I expect it is - once again - some random linker-generated stub
> > that ends up causing problems, where the re-link stage ends up being
> > unstable because of some subtle alignment issue or other. I think
> > zero-sized symbols have often been involved.
> 
> Linker-generated symbols are usually the cause, but those tend to
> be fixed with the extra pass, and Guenter said that doing an extra
> pass does not avoid the issue here.
> 
> I have not tried to understand what the 73bbb94466fd patch actually does,
> but as the description explains that it uses either 1-byte or
> 2-byte encodings for some symbols, I suspect this is related to
> the new problem here, possibly it gets into an oscillating state
> where making the symbol table shorter causes a symbol to use the
> longer representation in the next round, which in turn makes the
> table longer again.
> 
> What I've done in the past to debug this was to change
> scripts/link-vmlinux.sh to use a larger number of steps,
> mainly to see if it eventually converges, grows indefinitely
> or oscillates. After that I would compare the temporary files
> from the last two different steps to see which symbols are
> actually different. Unfortunately, there is no built-in
> debugging mode in kallsyms, so this is a rather manual process.
> 
I have been doing the same, but so far I never encountered the oscillating
situation. In those all I can find is that some symbol addresses keep
changing, but I have not been able to track down the cause. The possible
explanation above makes sense to me, but do you have an idea how I could
track down what actually happens ?

Thanks,
Guenter

  parent reply	other threads:[~2022-11-01 18:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-30 22:35 Linux 6.1-rc3 Linus Torvalds
2022-11-01  8:02 ` Build regressions/improvements in v6.1-rc3 Geert Uytterhoeven
2022-11-01  8:08   ` Geert Uytterhoeven
2022-11-01 17:00 ` Linux 6.1-rc3 Guenter Roeck
2022-11-01 17:29   ` Linus Torvalds
2022-11-01 17:37     ` Linus Torvalds
2022-11-01 17:57     ` Arnd Bergmann
2022-11-01 18:19       ` Miguel Ojeda
2022-11-01 18:26       ` Guenter Roeck [this message]
2022-11-01 18:37     ` Guenter Roeck
2023-02-02  7:40       ` Geert Uytterhoeven
2023-02-02  8:33         ` Geert Uytterhoeven

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=20221101182616.GA1328619@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=arnd@arndb.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=ojeda@kernel.org \
    --cc=rmk+kernel@armlinux.org.uk \
    --cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).