lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Wed, 17 Aug 2022 01:09:40 +0530 From: Naresh Kamboju <naresh.kamboju@...aro.org> To: Linus Torvalds <torvalds@...ux-foundation.org> Cc: open list <linux-kernel@...r.kernel.org>, Linux-Next Mailing List <linux-next@...r.kernel.org>, linux-fsdevel@...r.kernel.org, regressions@...ts.linux.dev, lkft-triage@...ts.linaro.org, Alexander Viro <viro@...iv.linux.org.uk>, Christian Brauner <christian.brauner@...ntu.com> Subject: Re: [next] arm64: kernel BUG at fs/inode.c:622 - Internal error: Oops - BUG: 0 - pc : clear_inode On Wed, 17 Aug 2022 at 00:40, Linus Torvalds <torvalds@...ux-foundation.org> wrote: > > On Tue, Aug 16, 2022 at 12:00 PM Naresh Kamboju > <naresh.kamboju@...aro.org> wrote: > > > > Following kernel BUG found while booting arm64 Qcom dragonboard 410c with > > Linux next-20220816 kernel Image. > > 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? This is a physical hardware db410c device. Following VIRTIO configs enabled. CONFIG_BLK_MQ_VIRTIO=y CONFIG_NET_9P_VIRTIO=y CONFIG_VIRTIO_BLK=y CONFIG_SCSI_VIRTIO=y CONFIG_VIRTIO_NET=y CONFIG_VIRTIO_CONSOLE=y CONFIG_VIRTIO_ANCHOR=y CONFIG_VIRTIO=y CONFIG_VIRTIO_PCI_LIB=y CONFIG_VIRTIO_PCI_LIB_LEGACY=y CONFIG_VIRTIO_MENU=y CONFIG_VIRTIO_PCI=y CONFIG_VIRTIO_PCI_LEGACY=y CONFIG_VIRTIO_BALLOON=y CONFIG_VIRTIO_MMIO=y CONFIG_CRYPTO_DEV_VIRTIO=y > > Do you see the same issue with plain v6.0-rc1? Nope. I do not notice reported BUG on v6.0-rc1. - Naresh
Powered by blists - more mailing lists