arm64: linux: stress-ng filename stressor crashes kernel
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Confirmed
|
High
|
Unassigned | ||
Mantic |
Won't Fix
|
High
|
Unassigned |
Bug Description
Running latest Ubuntu mantic (ext4 file system) with kernel: Linux mantic-arm64 6.5.0-7-generic #7-Ubuntu SMP PREEMPT_DYNAMIC Thu Sep 28 19:12:05 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux
How to reproduce:
Fire up a 24 instance ARM64 QEMU instance with Ubuntu Mantic Server. Install latest stress-ng from git repo:
sudo apt-get update
sudo apt-get build-dep stress-ng
git clone git://github.
cd stress-ng
make clean
make -j 24
make verify-test-all
When we reach the filename stressor the kernel crashes as follows:
[ 902.594715] kernel BUG at fs/dcache.c:2050!
[ 902.598205] Internal error: Oops - BUG: 00000000f2000800 [#1] SMP
[ 902.603127] Modules linked in: dccp_ipv4 dccp atm vfio_iommu_type1 vfio iommu
fd cmac algif_rng twofish_generic twofish_common serpent_generic fcrypt cast6_ge
neric cast5_generic cast_common camellia_generic blowfish_generic blowfish_commo
n aes_arm64 algif_skcipher algif_hash aria_generic sm4_generic sm4_neon ccm aes_
ce_ccm des_generic libdes authenc aegis128 algif_aead af_alg cfg80211 binfmt_mis
c nls_iso8859_1 dm_multipath drm efi_pstore dmi_sysfs qemu_fw_cfg ip_tables x_ta
bles autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy
async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 multipa
th linear crct10dif_ce polyval_ce polyval_generic ghash_ce sm4 sha2_ce sha256_ar
m64 sha1_ce arm_smccc_trng xhci_pci virtio_rng xhci_pci_renesas aes_neon_bs aes_
neon_blk aes_ce_blk aes_ce_cipher
[ 902.689941] CPU: 1 PID: 91317 Comm: stress-ng-filen Not tainted 6.5.0-7-gener
ic #7-Ubuntu
[ 902.699281] Hardware name: QEMU KVM Virtual Machine, BIOS 0.0.0 02/06/2015
[ 902.706902] pstate: 40400005 (nZcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[ 902.715488] pc : d_instantiate_
[ 902.720889] lr : ext4_add_
[ 902.725702] sp : ffff80008b6d3930
[ 902.729390] x29: ffff80008b6d3930 x28: 0000000000000000 x27: ffffbd164e51a980
[ 902.738705] x26: ffff6789f3b68f20 x25: 0000000000008180 x24: ffff678a541f7968
[ 902.747003] x23: ffff6789f3b68f00 x22: ffff80008b6d39b0 x21: ffff678a6a25bcb0
[ 902.755776] x20: ffff678a36f8f028 x19: 0000000000000000 x18: ffff80008af45068
[ 902.764647] x17: 0000000000000000 x16: 0000000000000000 x15: ecececececececec
[ 902.773135] x14: ecececececececec x13: ecececececececec x12: ecececececececec
[ 902.781386] x11: ecececececececec x10: ecececececececec x9 : ffffbd164d5990bc
[ 902.789346] x8 : 0000000000000000 x7 : 0000000000000000 x6 : 0000000000000000
[ 902.798564] x5 : 0000000000000000 x4 : 0000000000000000 x3 : 0000000000000000
[ 902.806851] x2 : ffffbd16504e4ce0 x1 : ffff678a36f8f028 x0 : ffff6789f3b68f00
[ 902.815544] Call trace:
[ 902.818870] d_instantiate_
[ 902.823523] ext4_create+
[ 902.827716] lookup_
[ 902.832480] open_last_
[ 902.837060] path_openat+
[ 902.840975] do_filp_
[ 902.845582] do_sys_
[ 902.850426] __arm64_
[ 902.854952] invoke_
[ 902.859155] el0_svc_
[ 902.864979] do_el0_
[ 902.869364] el0_svc+0x30/0xe0
[ 902.873401] el0t_64_
[ 902.878336] el0t_64_
[ 902.882513] Code: d2800002 d2800010 d2800011 d65f03c0 (d4210000)
[ 902.890632] ---[ end trace 0000000000000000 ]---
Changed in linux (Ubuntu Mantic): | |
status: | Incomplete → New |
Note that just running stress-ng with --filename 0 will reproduce the issue. I'm testing this now on a cleanly formatted ext4 file system