syzbot


BUG: unable to handle kernel paging request in xfs_destroy_mount_workqueues

Status: moderation: reported on 2024/10/27 01:42
Subsystems: xfs
[Documentation on labels]
Reported-by: syzbot+a9ebc8164aae37b8926a@syzkaller.appspotmail.com
First crash: 29d, last: 29d
Similar bugs (2)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream general protection fault in xfs_destroy_mount_workqueues xfs 46 129d 185d 0/28 auto-obsoleted due to no activity on 2024/09/23 05:54
upstream KASAN: slab-use-after-free Write in xfs_destroy_mount_workqueues xfs 1 602d 598d 0/28 closed as dup on 2023/04/03 05:23

Sample crash report:
XFS (loop0): Unmounting Filesystem a2f82aab-77f8-4286-afd4-a8f747a74bab
Unable to handle kernel paging request at virtual address f9943f801fffe003
KASAN: maybe wild-memory-access in range [0xcca5fc00ffff0018-0xcca5fc00ffff001f]
Mem abort info:
  ESR = 0x0000000096000004
  EC = 0x25: DABT (current EL), IL = 32 bits
  SET = 0, FnV = 0
  EA = 0, S1PTW = 0
  FSC = 0x04: level 0 translation fault
Data abort info:
  ISV = 0, ISS = 0x00000004, ISS2 = 0x00000000
  CM = 0, WnR = 0, TnD = 0, TagAccess = 0
  GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0
[f9943f801fffe003] address between user and kernel address ranges
Internal error: Oops: 0000000096000004 [#1] PREEMPT SMP
Modules linked in:
CPU: 0 UID: 0 PID: 6423 Comm: syz-executor Not tainted 6.12.0-rc4-syzkaller-g526116b79e8c #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
pstate: 804000c5 (Nzcv daIF +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : __lock_acquire+0xfc/0x77c8 kernel/locking/lockdep.c:5065
lr : lock_acquire+0x240/0x728 kernel/locking/lockdep.c:5825
sp : ffff8000a3b87620
x29: ffff8000a3b878e0 x28: ffff800080261d84 x27: 0000000000000000
x26: ffff0001b363a4c0 x25: 0000000000000000 x24: 0000000000000001
x23: 0000000000000000 x22: 1ffff00011f000ba x21: cca5fc00ffff0019
x20: 0000000000000001 x19: 0000000000000000 x18: ffff8000a3b87560
x17: 000000000002b9b4 x16: ffff8000830c7d0c x15: 0000000000000001
x14: ffff80008f8005d8 x13: dfff800000000000 x12: ffff700014770eec
x11: ffff80008035e028 x10: ffff80008f8005d4 x9 : 00000000000000f3
x8 : 1994bf801fffe003 x7 : ffff800080261d84 x6 : 0000000000000000
x5 : 0000000000000001 x4 : 0000000000000001 x3 : 0000000000000000
x2 : 0000000000000000 x1 : 0000000000000000 x0 : cca5fc00ffff0019
Call trace:
 __lock_acquire+0xfc/0x77c8 kernel/locking/lockdep.c:5065 (P)
 lock_acquire+0x240/0x728 kernel/locking/lockdep.c:5825 (L)
 lock_acquire+0x240/0x728 kernel/locking/lockdep.c:5825
 __raw_spin_lock_irq include/linux/spinlock_api_smp.h:119 [inline]
 _raw_spin_lock_irq+0x58/0x70 kernel/locking/spinlock.c:170
 put_pwq_unlocked kernel/workqueue.c:1662 [inline]
 destroy_workqueue+0x8d8/0xdc0 kernel/workqueue.c:5883
 xfs_destroy_mount_workqueues+0x3c/0xdc fs/xfs/xfs_super.c:601
 xfs_fs_put_super+0x114/0x130 fs/xfs/xfs_super.c:1152
 generic_shutdown_super+0x12c/0x2bc fs/super.c:642
 kill_block_super+0x44/0x90 fs/super.c:1696
 xfs_kill_sb+0x20/0x58 fs/xfs/xfs_super.c:2056
 deactivate_locked_super+0xc4/0x12c fs/super.c:473
 deactivate_super+0xe0/0x100 fs/super.c:506
 cleanup_mnt+0x34c/0x3dc fs/namespace.c:1373
 __cleanup_mnt+0x20/0x30 fs/namespace.c:1380
 task_work_run+0x230/0x2e0 kernel/task_work.c:239
 resume_user_mode_work include/linux/resume_user_mode.h:50 [inline]
 do_notify_resume+0x178/0x1f4 arch/arm64/kernel/entry-common.c:151
 exit_to_user_mode_prepare arch/arm64/kernel/entry-common.c:169 [inline]
 exit_to_user_mode arch/arm64/kernel/entry-common.c:178 [inline]
 el0_svc+0xac/0x168 arch/arm64/kernel/entry-common.c:745
 el0t_64_sync_handler+0x84/0x108 arch/arm64/kernel/entry-common.c:762
 el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:600
Code: d007a508 b945d508 34008c88 d343fea8 (386d6908) 
---[ end trace 0000000000000000 ]---
----------------
Code disassembly (best guess):
   0:	d007a508 	adrp	x8, 0xf4a2000
   4:	b945d508 	ldr	w8, [x8, #1492]
   8:	34008c88 	cbz	w8, 0x1198
   c:	d343fea8 	lsr	x8, x21, #3
* 10:	386d6908 	ldrb	w8, [x8, x13] <-- trapping instruction

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/10/23 01:30 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 526116b79e8c 9d74f456 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 BUG: unable to handle kernel paging request in xfs_destroy_mount_workqueues
* Struck through repros no longer work on HEAD.