Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Feedback-ID: idc91472f:Fastmail
Date:   Thu, 19 Jan 2023 09:29:20 +0100
From:   Klaus Jensen <its@irrelevant.dk>
To:     Martin Wilck <mwilck@suse.com>
Cc:     Christoph Hellwig <hch@lst.de>, Keith Busch <kbusch@kernel.org>,
        Jens Axboe <axboe@fb.com>, Sagi Grimberg <sagi@grimberg.me>,
        linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org,
        Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
        "Rafael J. Wysocki" <rafael@kernel.org>
Subject: Re: regression on aarch64? panic on boot
Message-ID: <Y8j/YLA9O7Q+haE/@cormorant.local>
References: <Y8XINx8fpGPKudW6@cormorant.local>
 <20230117055819.GB13795@lst.de>
 <Y8ZA30EoAFaFPwVC@cormorant.local>
 <20230117063735.GA14468@lst.de>
 <59599137a9556355cb43563a4fbcc05b0fe769b4.camel@suse.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
        protocol="application/pgp-signature"; boundary="/wMxtvFL3yVWbTgo"
Content-Disposition: inline
In-Reply-To: <59599137a9556355cb43563a4fbcc05b0fe769b4.camel@suse.com>
Precedence: bulk


--/wMxtvFL3yVWbTgo
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Jan 17 13:11, Martin Wilck wrote:
> On Tue, 2023-01-17 at 07:37 +0100, Christoph Hellwig wrote:
> > On Tue, Jan 17, 2023 at 07:31:59AM +0100, Klaus Jensen wrote:
> > > Good morning Christoph,
> > >=20
> > > Yep, the above works.
> >=20
> > Context for the newly added: This is dropping the newly added
> > PROBE_PREFER_ASYNCHRONOUS in nvme, which causes Klaus' arm64 (but not
> > other boot tests) to fail.=C2=A0 Any idea what could be going wrong the=
re
> > probably in userspace?
>=20
> If this is an aarch64 userspace issue, maybe related to
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D107678 ?
>=20
> That bug causes segfaults of user space programs if for some reason the
> unwind code is invoked. It happens only if libgcc_s.so is compiled with
> gcc 13, and the pauth CPU feature is enabled in qemu.
>=20
> Martin
>=20

I just observed the same panic on qemu emulated ppc64 as well. It's
pretty rare, maybe 1 in 20. 'rootwait' or removing the the prefer
asynchronous probe fixes it as well.

--/wMxtvFL3yVWbTgo
Content-Type: application/pgp-signature; name="signature.asc"

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

iQEzBAEBCgAdFiEEUigzqnXi3OaiR2bATeGvMW1PDekFAmPI/18ACgkQTeGvMW1P
DelXYAf9H5/rtUW2fNjGQYkeNQY3NOPT2QtRx6Ix2uuwGaM5ICTJCK97IE7ZMCZ9
yAIgFKDJc9Cyho+FnlzmTWYWVxIXDoQQktj3fUrFSRajxRBzVTJynC8m9O0We6cm
YBJvPxpfjOfst5SAq3PVjTX6r88xd4FPfbm0r11efWp0U0egEt6HpeUFA1hnPjoL
jsH062D2VVDEAM5pi2tSeKbWi1CLt5pN+aC16Q64x3zQUcTjh1T/QHGPii0Gjjsh
ds0d3lZA4WGUstS+ufRtZno+wQt/qW8lekGBidIaAmuUhVpupbaOzirNkNc8FGGR
5/YSRyr/+v4A3Z7tNo5hp36wfB/yQw==
=cc4b
-----END PGP SIGNATURE-----

--/wMxtvFL3yVWbTgo--