Hello,
syzbot found the following issue on:
HEAD commit: 3a5928702e71 Linux 5.15.167
git tree: linux-5.15.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=12d5e207980000
kernel config:
https://syzkaller.appspot.com/x/.config?x=171882977b524c53
dashboard link:
https://syzkaller.appspot.com/bug?extid=c80d64708c6855389daa
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/22ee27cb312d/disk-3a592870.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/90bf6a3e3d20/vmlinux-3a592870.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/096dd2c73ac3/Image-3a592870.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+c80d64...@syzkaller.appspotmail.com
------------[ cut here ]------------
WARNING: CPU: 1 PID: 5887 at fs/btrfs/inode.c:4167 __btrfs_unlink_inode+0x950/0xb3c fs/btrfs/inode.c:4167
Modules linked in:
CPU: 1 PID: 5887 Comm: syz.4.350 Not tainted 5.15.167-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024
pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : __btrfs_unlink_inode+0x950/0xb3c fs/btrfs/inode.c:4167
lr : __btrfs_unlink_inode+0x950/0xb3c fs/btrfs/inode.c:4167
sp : ffff8000208679c0
x29: ffff800020867a60 x28: ffff800020867a20 x27: 1ffff0000410cf40
x26: 0000000000000104 x25: 00000000fffffff4 x24: ffff0000c0fd6d10
x23: ffff0000e64306e0 x22: 1ffff0000410cf44 x21: dfff800000000000
x20: 1fffe0001cc860e7 x19: ffff0000e6430738 x18: 0000000000000001
x17: 0000000000000000 x16: ffff800011ac23e0 x15: 00000000ffffffff
x14: ffff0000cba50000 x13: 0000000000000001 x12: 0000000000000001
x11: 0000000000000000 x10: 0000000000000000 x9 : 4d0a6e7a7531b500
x8 : 4d0a6e7a7531b500 x7 : 0000000000000001 x6 : 0000000000000001
x5 : ffff800020867138 x4 : ffff800014b9fae0 x3 : ffff800008557c4c
x2 : 0000000000000001 x1 : 0000000100000000 x0 : 0000000000000026
Call trace:
__btrfs_unlink_inode+0x950/0xb3c fs/btrfs/inode.c:4167
btrfs_unlink_inode fs/btrfs/inode.c:4215 [inline]
btrfs_unlink+0x10c/0x254 fs/btrfs/inode.c:4258
vfs_unlink+0x2f0/0x508 fs/namei.c:4280
do_unlinkat+0x4cc/0x830 fs/namei.c:4348
__do_sys_unlinkat fs/namei.c:4391 [inline]
__se_sys_unlinkat fs/namei.c:4384 [inline]
__arm64_sys_unlinkat+0xcc/0xfc fs/namei.c:4384
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:608
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:626
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
irq event stamp: 82010
hardirqs last enabled at (82009): [<ffff80000832c17c>] __up_console_sem+0xb4/0x100 kernel/printk/printk.c:257
hardirqs last disabled at (82010): [<ffff800011abda6c>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:396
softirqs last enabled at (81986): [<ffff8000081b6d74>] softirq_handle_end kernel/softirq.c:401 [inline]
softirqs last enabled at (81986): [<ffff8000081b6d74>] handle_softirqs+0xb88/0xdbc kernel/softirq.c:586
softirqs last disabled at (81881): [<ffff8000081b740c>] __do_softirq kernel/softirq.c:592 [inline]
softirqs last disabled at (81881): [<ffff8000081b740c>] do_softirq_own_stack include/asm-generic/softirq_stack.h:10 [inline]
softirqs last disabled at (81881): [<ffff8000081b740c>] invoke_softirq kernel/softirq.c:439 [inline]
softirqs last disabled at (81881): [<ffff8000081b740c>] __irq_exit_rcu+0x268/0x4d8 kernel/softirq.c:641
---[ end trace 45418c6a8f0a94c2 ]---
BTRFS: error (device loop4) in __btrfs_unlink_inode:4167: errno=-12 Out of memory
BTRFS info (device loop4): forced readonly
---
This report is generated by a bot. It may contain errors.
See
https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at
syzk...@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup