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;
Date:   Wed, 17 Aug 2022 12:00:51 +1000
From:   Stephen Rothwell <sfr@rothwell.id.au>
To:     Naresh Kamboju <naresh.kamboju@linaro.org>
Cc:     Linus Torvalds <torvalds@linux-foundation.org>,
        open list <linux-kernel@vger.kernel.org>,
        Linux-Next Mailing List <linux-next@vger.kernel.org>,
        linux-fsdevel@vger.kernel.org, regressions@lists.linux.dev,
        lkft-triage@lists.linaro.org,
        Alexander Viro <viro@zeniv.linux.org.uk>,
        Christian Brauner <christian.brauner@ubuntu.com>
Subject: Re: [next] arm64: kernel BUG at fs/inode.c:622 - Internal error:
 Oops - BUG: 0 - pc : clear_inode
Message-ID: <20220817120051.20a39b52@oak.ozlabs.ibm.com>
In-Reply-To: <CA+G9fYuLvTmVbyEpU3vrw58QaWfN=Eg8VdrdRei_jmu2Y2OzOg@mail.gmail.com>
References: <CA+G9fYv2Wof_Z4j8wGYapzngei_NjtnGUomb7y34h4VDjrQDBA@mail.gmail.com>
        <CAHk-=wj=u9+0kitx6Z=efRDrGVu_OSUieenyK4ih=TFjZdyMYQ@mail.gmail.com>
        <CA+G9fYuLvTmVbyEpU3vrw58QaWfN=Eg8VdrdRei_jmu2Y2OzOg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="Sig_/p7uJ_iQfq=MtmPXdTyKBMw9";
 protocol="application/pgp-signature"; micalg=pgp-sha256
Precedence: bulk

--Sig_/p7uJ_iQfq=MtmPXdTyKBMw9
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

Hi Naresh,

On Wed, 17 Aug 2022 01:09:40 +0530 Naresh Kamboju <naresh.kamboju@linaro.or=
g> wrote:
>
> On Wed, 17 Aug 2022 at 00:40, Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
> >
> > On Tue, Aug 16, 2022 at 12:00 PM Naresh Kamboju
> > <naresh.kamboju@linaro.org> wrote: =20
> > >
> > > Following kernel BUG found while booting arm64 Qcom dragonboard 410c =
with
> > > Linux next-20220816 kernel Image. =20
> >
> > What kind of environment is this?
> >
> > Havign that inode list corruption makes it smell a *bit* like the
> > crazy memory corruption that we saw with the google cloud instances,
> > but that would only happen wif you actually use VIRTIO for your
> > environment? =20
>=20
> This is a physical hardware db410c device.
> Following VIRTIO configs enabled.
>=20
> CONFIG_BLK_MQ_VIRTIO=3Dy
> CONFIG_NET_9P_VIRTIO=3Dy
> CONFIG_VIRTIO_BLK=3Dy
> CONFIG_SCSI_VIRTIO=3Dy
> CONFIG_VIRTIO_NET=3Dy
> CONFIG_VIRTIO_CONSOLE=3Dy
> CONFIG_VIRTIO_ANCHOR=3Dy
> CONFIG_VIRTIO=3Dy
> CONFIG_VIRTIO_PCI_LIB=3Dy
> CONFIG_VIRTIO_PCI_LIB_LEGACY=3Dy
> CONFIG_VIRTIO_MENU=3Dy
> CONFIG_VIRTIO_PCI=3Dy
> CONFIG_VIRTIO_PCI_LEGACY=3Dy
> CONFIG_VIRTIO_BALLOON=3Dy
> CONFIG_VIRTIO_MMIO=3Dy
> CONFIG_CRYPTO_DEV_VIRTIO=3Dy
>=20
>=20
> >
> > Do you see the same issue with plain v6.0-rc1? =20
>=20
> Nope. I do not notice reported BUG on v6.0-rc1.

Is it reliable enough that you could possibly do a bisection between
v6.0-rc1 and next-20220816?

--=20
Cheers,
Stephen Rothwell

--Sig_/p7uJ_iQfq=MtmPXdTyKBMw9
Content-Type: application/pgp-signature
Content-Description: OpenPGP digital signature

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

iQEzBAEBCAAdFiEENIC96giZ81tWdLgKAVBC80lX0GwFAmL8S9MACgkQAVBC80lX
0GzZAQf7Bsp+3irXdvFTPbeYTsFim8hgA9o1L4+3TfIVF5sd1bGcCdpcN20fck2P
7viuEA5w5CXL1S2W6wzMmgKu7TwkhXHvbAGgPIGACHtGaCRjZXdix+sxlO/qX+ly
HdhuvbqFkRW2ed+fj09Ww4KJgGP8/l0zwFemnBOrqao+cwIuNfKsQdbGVyzM43hr
5PttxYZwGZvHar5BjSCqUM2MJ93i5s6frfJkreYg20gWCGaDOx3eZ468gSGPNw4t
e6G/sdlX8e2aB0hhOuF4Fjn09vp5paWMelkEjEPbBlsgRsV04PmvNjEg0nKn8haJ
0Ymh4ddoHGM2pz1ODoXplzCO8ap7uQ==
=q9S1
-----END PGP SIGNATURE-----

--Sig_/p7uJ_iQfq=MtmPXdTyKBMw9--