Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) client-ip=2620:137:e000::1:18;
Date:   Tue, 15 Mar 2022 13:32:49 +1100
From:   Stephen Rothwell <sfr@canb.auug.org.au>
To:     Thomas Gleixner <tglx@linutronix.de>,
        Ingo Molnar <mingo@redhat.com>,
        "H. Peter Anvin" <hpa@zytor.com>,
        Peter Zijlstra <peterz@infradead.org>
Cc:     Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warnings after merge of the tip tree
Message-ID: <20220315133249.146b8bac@canb.auug.org.au>
In-Reply-To: <20220122105806.3b710900@canb.auug.org.au>
References: <20211217144004.0c00fabc@canb.auug.org.au>
        <20220122105806.3b710900@canb.auug.org.au>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="Sig_/fa=9QQeq4JL5lCcjlNPD_LS";
 protocol="application/pgp-signature"; micalg=pgp-sha256
Precedence: bulk

--Sig_/fa=9QQeq4JL5lCcjlNPD_LS
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

Hi all,

On Sat, 22 Jan 2022 10:58:06 +1100 Stephen Rothwell <sfr@canb.auug.org.au> =
wrote:
>
> On Fri, 17 Dec 2021 14:40:04 +1100 Stephen Rothwell <sfr@canb.auug.org.au=
> wrote:
> >
> > After merging the tip tree, today's linux-next build (x86_64 allmodconf=
ig)
> > produced these warnings:
> >=20
> > lib/strnlen_user.o: warning: objtool: strnlen_user()+0xc9: call to do_s=
trnlen_user() with UACCESS enabled
> > lib/strncpy_from_user.o: warning: objtool: strncpy_from_user()+0x129: c=
all to do_strncpy_from_user() with UACCESS enabled
> > vmlinux.o: warning: objtool: mce_start()+0x5c: call to __kasan_check_wr=
ite() leaves .noinstr.text section
> > vmlinux.o: warning: objtool: mce_gather_info()+0x5f: call to v8086_mode=
.constprop.0() leaves .noinstr.text section
> > vmlinux.o: warning: objtool: mce_read_aux()+0x8a: call to mca_msr_reg()=
 leaves .noinstr.text section
> > vmlinux.o: warning: objtool: do_machine_check()+0x192: call to mce_no_w=
ay_out() leaves .noinstr.text section
> > vmlinux.o: warning: objtool: mce_severity_amd.constprop.0()+0xca: call =
to mce_severity_amd_smca() leaves .noinstr.text section
> >=20
> > I am not sure which changes caused the above. =20
>=20
> I currently still get the following warnings from an x86_64
> allmodconfig build fo Linus' tree:
>=20
> vmlinux.o: warning: objtool: mce_start()+0x5c: call to __kasan_check_writ=
e() leaves .noinstr.text section
> vmlinux.o: warning: objtool: mce_gather_info()+0x5f: call to v8086_mode.c=
onstprop.0() leaves .noinstr.text section
> vmlinux.o: warning: objtool: mce_read_aux()+0x8a: call to mca_msr_reg() l=
eaves .noinstr.text section
> vmlinux.o: warning: objtool: do_machine_check()+0x192: call to mce_no_way=
_out() leaves .noinstr.text section
> vmlinux.o: warning: objtool: mce_severity_amd.constprop.0()+0xca: call to=
 mce_severity_amd_smca() leaves .noinstr.text section
>=20
> $ x86_64-linux-gnu-gcc --version
> x86_64-linux-gnu-gcc (Debian 11.2.0-9) 11.2.0
> $ x86_64-linux-gnu-ld --version
> GNU ld (GNU Binutils for Debian) 2.37

I gained these new ones after merging today's tip tree:

arch/x86/crypto/chacha-x86_64.o: warning: objtool: chacha_2block_xor_avx512=
vl() falls through to next function chacha_8block_xor_avx512vl()
arch/x86/crypto/chacha-x86_64.o: warning: objtool: chacha_4block_xor_avx512=
vl() falls through to next function chacha_8block_xor_avx512vl()
arch/x86/crypto/poly1305-x86_64.o: warning: objtool: poly1305_blocks_avx() =
falls through to next function poly1305_blocks_x86_64()
arch/x86/crypto/poly1305-x86_64.o: warning: objtool: poly1305_emit_avx() fa=
lls through to next function poly1305_emit_x86_64()
arch/x86/crypto/poly1305-x86_64.o: warning: objtool: poly1305_blocks_avx2()=
 falls through to next function poly1305_blocks_x86_64()
arch/x86/crypto/poly1305-x86_64.o: warning: objtool: poly1305_blocks_avx512=
() falls through to next function poly1305_blocks_x86_64()

--=20
Cheers,
Stephen Rothwell

--Sig_/fa=9QQeq4JL5lCcjlNPD_LS
Content-Type: application/pgp-signature
Content-Description: OpenPGP digital signature

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEENIC96giZ81tWdLgKAVBC80lX0GwFAmIv+tEACgkQAVBC80lX
0GyRBAgAgmNjs0824Yd3XY9U01ZlbgSDODCHolJelw5GH0KrBuYJd4z426YLBNsi
eeeZxyOUoBI4YH5xxLY+4XJWT1xokLz4OqcpzOvWui8kbFl1lajz3lF6MZRkwS/g
1LaapEmAXwBGHEmfbXF26uhUaEJnAwXLmQ8dZBZlr07bJ6/NUJ00kQp/1PSHrdLX
8i91tyvKTQJvadpL16CZgU+L3XbqtzPFadAk1xQnfh+lQ+Xw8H2TkGim+BQ+wJ+r
w0T0Zz96erB1OTTvhpRnSvHfa+wPu0pJ5qbLe9l2kD4L9BauH87Kewz7raefgTt1
BRKoPj6PuNY61vqN6Ru5Ad+mGyrSbQ==
=yJOT
-----END PGP SIGNATURE-----

--Sig_/fa=9QQeq4JL5lCcjlNPD_LS--