From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Guenter Roeck <linux@roeck-us.net>,
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>,
Boqun Feng <boqun.feng@gmail.com>
Subject: Re: Linux 6.1-rc3
Date: Tue, 1 Nov 2022 19:19:18 +0100 [thread overview]
Message-ID: <CANiq72nfpdhPgEgWbz2T7C3GOk94mPbcqfvXTp3Lp=qRvtON9g@mail.gmail.com> (raw)
In-Reply-To: <29d07648-29a9-432a-a666-f9c9e55c32f6@app.fastmail.com>
On Tue, Nov 1, 2022 at 6:58 PM Arnd Bergmann <arnd@arndb.de> wrote:
>
> 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 been trying to reproduce the issue on my side, trying to match
Guenter's environment, but so far I have not been successful, even
when running the toolchain binaries he sent me (thanks a lot!).
What I could reproduce easily, though, was one from the kernel test
robot, powerpc as well, in 5.15.y [1] It requires 4 passes (i.e.
KALLSYMS_EXTRA_PASS is not enough), but it is not an oscillating one.
[1] https://lore.kernel.org/lkml/202209241418.35P6OMjS-lkp@intel.com/
> 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.
Does that mean you saw the oscillating one in the past? Guenter thinks
it is a new issue, since he never saw the oscillating case.
If you did see it, then it may be the case that the kallsyms changes
make some edge case more likely -- at least this is what Boqun and I
originally thought.
Cheers,
Miguel
next prev parent reply other threads:[~2022-11-01 18:19 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 [this message]
2022-11-01 18:26 ` Guenter Roeck
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='CANiq72nfpdhPgEgWbz2T7C3GOk94mPbcqfvXTp3Lp=qRvtON9g@mail.gmail.com' \
--to=miguel.ojeda.sandonis@gmail.com \
--cc=arnd@arndb.de \
--cc=boqun.feng@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--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).