Hello,
syzbot found the following issue on:
HEAD commit: 2a910f4af54d Linux 5.15.139
git tree: linux-5.15.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=1496a4d8e80000
kernel config:
https://syzkaller.appspot.com/x/.config?x=f754f36f723b24c9
dashboard link:
https://syzkaller.appspot.com/bug?extid=d5bdb5468b410028e316
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/dc1499a9b3f1/disk-2a910f4a.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/6eae774ea732/vmlinux-2a910f4a.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/92b598f89518/Image-2a910f4a.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+d5bdb5...@syzkaller.appspotmail.com
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
------------[ cut here ]------------
WARNING: CPU: 1 PID: 19453 at fs/btrfs/qgroup.c:1009 btrfs_quota_enable+0x10d8/0x18d0 fs/btrfs/qgroup.c:1009
Modules linked in:
CPU: 1 PID: 19453 Comm: syz-executor.5 Not tainted 5.15.139-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/09/2023
pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : btrfs_quota_enable+0x10d8/0x18d0 fs/btrfs/qgroup.c:1009
lr : btrfs_quota_enable+0x10d8/0x18d0 fs/btrfs/qgroup.c:1009
sp : ffff800022477aa0
x29: ffff800022477c20 x28: dfff800000000000 x27: ffff70000448ef68
x26: ffff0001184f0048 x25: fffffffffffffff4 x24: ffff0001184f1798
x23: ffff0000c2fb3400 x22: ffff00011ee245d8 x21: ffff800022477b40
x20: 1fffe00023dc48bb x19: ffff00011ee24580 x18: 0000000000000001
x17: ff80800008335e48 x16: 0000000000000002 x15: ffff800008335e48
x14: 00000000ffffffff x13: ffffffffffffffff x12: 0000000000040000
x11: 000000000000cd7a x10: ffff80001d179000 x9 : 4ec7b6355d4ad400
x8 : 4ec7b6355d4ad400 x7 : 0000000000000001 x6 : 0000000000000001
x5 : ffff800022477218 x4 : ffff8000149ff8a0 x3 : ffff800008335f94
x2 : 0000000000000001 x1 : 0000000100000000 x0 : 0000000000000026
Call trace:
btrfs_quota_enable+0x10d8/0x18d0 fs/btrfs/qgroup.c:1009
btrfs_ioctl_quota_ctl+0x144/0x188 fs/btrfs/ioctl.c:4228
btrfs_ioctl+0x9cc/0xa5c fs/btrfs/ioctl.c:5011
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:874 [inline]
__se_sys_ioctl fs/ioctl.c:860 [inline]
__arm64_sys_ioctl+0x14c/0x1c8 fs/ioctl.c:860
__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: 80326
hardirqs last enabled at (80325): [<ffff80000832bad4>] __up_console_sem+0xb4/0x100 kernel/printk/printk.c:257
hardirqs last disabled at (80326): [<ffff80001196ec28>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:396
softirqs last enabled at (80306): [<ffff800008020ccc>] softirq_handle_end kernel/softirq.c:401 [inline]
softirqs last enabled at (80306): [<ffff800008020ccc>] __do_softirq+0xb5c/0xe20 kernel/softirq.c:587
softirqs last disabled at (80269): [<ffff8000081b5750>] do_softirq_own_stack include/asm-generic/softirq_stack.h:10 [inline]
softirqs last disabled at (80269): [<ffff8000081b5750>] invoke_softirq kernel/softirq.c:439 [inline]
softirqs last disabled at (80269): [<ffff8000081b5750>] __irq_exit_rcu+0x28c/0x534 kernel/softirq.c:637
---[ end trace b21b203f47b6aa71 ]---
BTRFS: error (device loop5) in btrfs_quota_enable:1009: errno=-12 Out of memory
BTRFS info (device loop5): 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