linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Linux ARM <linux-arm-kernel@lists.infradead.org>,
	Linux Kernel Build System <linux-kbuild@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Regressions <regressions@lists.linux.dev>,
	Linux EFI <linux-efi@vger.kernel.org>
Cc: Masahiro Yamada <masahiroy@kernel.org>,
	Ard Biesheuvel <ardb@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Alan Bartlett <ajb@elrepo.org>
Subject: Fwd: Regression. -6.3.X Good. -6.4-rcY Bad.
Date: Mon, 22 May 2023 07:23:00 +0700	[thread overview]
Message-ID: <8a79151b-ef75-08ad-ae3d-f6cdabfeaa47@gmail.com> (raw)

Hi,

I notice a simple build-time regression on Bugzilla [1]. Quoting from it:

> This is a very simple to see regression.
> 
> On arm64 hardware, take any one of the -6.4-rcY tarballs created by Linus. Extract the contents of the tarball and cd to the linux-6.4-rcY directory. Issue a "make clean" or a "make mrproper" or a "make distclean" command. Look at the output (there should not be any). In every case, the output is --
> 
> nm: 'vmlinux': No such file
> 
> A bisection of Linus' full tree was performed specifying v6.4-rc1 as bad and v6.3 as good. Here is the result --
> 
> git bisect start
> # status: waiting for both good and bad commits
> # bad: [ac9a78681b921877518763ba0e89202254349d1b] Linux 6.4-rc1
> git bisect bad ac9a78681b921877518763ba0e89202254349d1b
> # status: waiting for good commit(s), bad commit known
> # good: [457391b0380335d5e9a5babdec90ac53928b23b4] Linux 6.3
> git bisect good 457391b0380335d5e9a5babdec90ac53928b23b4
> # good: [6e98b09da931a00bf4e0477d0fa52748bf28fcce] Merge tag 'net-next-6.4' of git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next
> git bisect good 6e98b09da931a00bf4e0477d0fa52748bf28fcce
> # good: [70cc1b5307e8ee3076fdf2ecbeb89eb973aa0ff7] Merge tag 'powerpc-6.4-1' of git://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux
> git bisect good 70cc1b5307e8ee3076fdf2ecbeb89eb973aa0ff7
> # bad: [865fdb08197e657c59e74a35fa32362b12397f58] Merge tag 'input-for-v6.4-rc0' of git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input
> git bisect bad 865fdb08197e657c59e74a35fa32362b12397f58
> # good: [e81507acdc19d91df4121f409871f3e4e055f6c2] Merge tag 'clk-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/clk/linux
> git bisect good e81507acdc19d91df4121f409871f3e4e055f6c2
> # bad: [26c009dffca89b0f8fe7facc41d1ccf88a66825a] Merge tag '6.4-rc-smb3-client-fixes-part1' of git://git.samba.org/sfrench/cifs-2.6
> git bisect bad 26c009dffca89b0f8fe7facc41d1ccf88a66825a
> # bad: [10de638d8ea57ebab4231ea077bed01d9bade775] Merge tag 's390-6.4-1' of git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux
> git bisect bad 10de638d8ea57ebab4231ea077bed01d9bade775
> # good: [680957b3b8b0b2e8697592fcb77369d4f643908a] s390/relocate_kernel: use SYM* macros instead of ENTRY(), etc.
> git bisect good 680957b3b8b0b2e8697592fcb77369d4f643908a
> # good: [ea76e08f4d901a450619831a255e9e0a4c0ed162] rust: ioctl: Add ioctl number manipulation functions
> git bisect good ea76e08f4d901a450619831a255e9e0a4c0ed162
> # bad: [825a0714d2b3883d4f8ff64f6933fb73ee3f1834] Merge tag 'efi-next-for-v6.4' of git://git.kernel.org/pub/scm/linux/kernel/git/efi/efi
> git bisect bad 825a0714d2b3883d4f8ff64f6933fb73ee3f1834
> # good: [9489d1bdb763a3dd954e61522043190a9fd1cb4c] power: supply: generic-adc-battery: simplify read_channel logic
> git bisect good 9489d1bdb763a3dd954e61522043190a9fd1cb4c
> # good: [528bd42615f4bb564613cc76dead90d7fbae76ba] power: supply: rk817: Drop unneeded debugging code
> git bisect good 528bd42615f4bb564613cc76dead90d7fbae76ba
> # good: [538bc0f40b364f2c7b81f11aa163f723b138b40f] efi/zboot: Set forward edge CFI compat header flag if supported
> git bisect good 538bc0f40b364f2c7b81f11aa163f723b138b40f
> # bad: [026b85796ab4d52af56f8a1c60d2613983ecd845] efi/zboot: arm64: Grab code size from ELF symbol in payload
> git bisect bad 026b85796ab4d52af56f8a1c60d2613983ecd845
> # bad: [45dd403da851124412d32e3193c21de4a51d29da] efi/zboot: arm64: Inject kernel code size symbol into the zboot payload
> git bisect bad 45dd403da851124412d32e3193c21de4a51d29da
> # first bad commit: [45dd403da851124412d32e3193c21de4a51d29da] efi/zboot: arm64: Inject kernel code size symbol into the zboot payload
> 
> Reverting the commit 45dd403da851124412d32e3193c21de4a51d29da resolves the problem.

The regression looks like arm-specific, but the first bad commit
IMO isn't related to kbuild system.

Anyway, I'm adding it to regzbot:

#regzbot introduced: 45dd403da85112 https://bugzilla.kernel.org/show_bug.cgi?id=217468
#regzbot title: nm vmlinux ENOENT when "make mrproper" on arm64

Thanks.

[1]: https://bugzilla.kernel.org/show_bug.cgi?id=217468

-- 
An old man doll... just what I always wanted! - Clara

             reply	other threads:[~2023-05-22  0:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-22  0:23 Bagas Sanjaya [this message]
2023-05-22  1:15 ` Regression. -6.3.X Good. -6.4-rcY Bad Pedro Falcato
2023-05-22  6:33   ` Ard Biesheuvel
2023-05-22  6:45     ` Bagas Sanjaya

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=8a79151b-ef75-08ad-ae3d-f6cdabfeaa47@gmail.com \
    --to=bagasdotme@gmail.com \
    --cc=ajb@elrepo.org \
    --cc=ardb@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=masahiroy@kernel.org \
    --cc=regressions@lists.linux.dev \
    /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).