[v5.15] WARNING in btrfs_commit_transaction

6 views
Skip to first unread message

syzbot

unread,
Apr 16, 2023, 9:21:44 PM4/16/23
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 4fdad925aa1a Linux 5.15.107
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=155610fbc80000
kernel config: https://syzkaller.appspot.com/x/.config?x=d67d6c9042bf5bb9
dashboard link: https://syzkaller.appspot.com/bug?extid=58e860029d947f85076a
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/a4ecac695096/disk-4fdad925.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/3362687e1660/vmlinux-4fdad925.xz
kernel image: https://storage.googleapis.com/syzbot-assets/3e588c974210/Image-4fdad925.gz.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+58e860...@syzkaller.appspotmail.com

el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:614
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
BTRFS warning (device loop3): Skipping commit of aborted transaction.
------------[ cut here ]------------
WARNING: CPU: 0 PID: 6934 at fs/btrfs/transaction.c:2011 cleanup_transaction fs/btrfs/transaction.c:2011 [inline]
WARNING: CPU: 0 PID: 6934 at fs/btrfs/transaction.c:2011 btrfs_commit_transaction+0x1e04/0x30f0 fs/btrfs/transaction.c:2519
Modules linked in:
CPU: 0 PID: 6934 Comm: syz-executor.3 Not tainted 5.15.107-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : cleanup_transaction fs/btrfs/transaction.c:2011 [inline]
pc : btrfs_commit_transaction+0x1e04/0x30f0 fs/btrfs/transaction.c:2519
lr : cleanup_transaction fs/btrfs/transaction.c:2011 [inline]
lr : btrfs_commit_transaction+0x1e04/0x30f0 fs/btrfs/transaction.c:2519
sp : ffff8000228775c0
x29: ffff800022877800 x28: ffff000128f51100 x27: ffff0000d58e2024
x26: 00000000fffffff4 x25: ffff0000d58e2000 x24: ffff0000d8880000
x23: ffff0000dca69a50 x22: ffff0000dca69aa8 x21: ffff0000d88819d0
x20: 0000000000000000 x19: dfff800000000000 x18: 0000000000000001
x17: ff80800008333ebc x16: ffff800011943d44 x15: ffff800008333ebc
x14: 00000000ffffffff x13: ffffffffffffffff x12: 0000000000040000
x11: 0000000000010154 x10: ffff800022cbb000 x9 : 6078e9cd3f3abe00
x8 : 6078e9cd3f3abe00 x7 : 0000000000000001 x6 : 0000000000000001
x5 : ffff800022876d38 x4 : ffff8000149af940 x3 : ffff80000854a4a4
x2 : 0000000000000001 x1 : 0000000100000000 x0 : 0000000000000026
Call trace:
cleanup_transaction fs/btrfs/transaction.c:2011 [inline]
btrfs_commit_transaction+0x1e04/0x30f0 fs/btrfs/transaction.c:2519
btrfs_sync_fs+0x678/0xc94 fs/btrfs/super.c:1454
sync_filesystem+0x1a0/0x218 fs/sync.c:66
btrfs_remount+0x19c/0x1308 fs/btrfs/super.c:1930
legacy_reconfigure+0xfc/0x114 fs/fs_context.c:633
reconfigure_super+0x340/0x690 fs/super.c:916
do_remount fs/namespace.c:2656 [inline]
path_mount+0xc94/0x104c fs/namespace.c:3316
do_mount fs/namespace.c:3337 [inline]
__do_sys_mount fs/namespace.c:3545 [inline]
__se_sys_mount fs/namespace.c:3522 [inline]
__arm64_sys_mount+0x510/0x5e0 fs/namespace.c:3522
__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:596
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:614
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
irq event stamp: 81286
hardirqs last enabled at (81285): [<ffff800008329afc>] __up_console_sem+0xb4/0x100 kernel/printk/printk.c:257
hardirqs last disabled at (81286): [<ffff80001193f3d8>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:387
softirqs last enabled at (81248): [<ffff800008020ccc>] softirq_handle_end kernel/softirq.c:401 [inline]
softirqs last enabled at (81248): [<ffff800008020ccc>] __do_softirq+0xb5c/0xe20 kernel/softirq.c:587
softirqs last disabled at (81197): [<ffff8000081b56e0>] do_softirq_own_stack include/asm-generic/softirq_stack.h:10 [inline]
softirqs last disabled at (81197): [<ffff8000081b56e0>] invoke_softirq kernel/softirq.c:439 [inline]
softirqs last disabled at (81197): [<ffff8000081b56e0>] __irq_exit_rcu+0x28c/0x534 kernel/softirq.c:636
---[ end trace 83e4d06f5f324da9 ]---
BTRFS: error (device loop3) in cleanup_transaction:2011: errno=-12 Out of memory
BTRFS info (device loop3): forced readonly
BTRFS error (device loop3): Remounting read-write after error is not allowed


---
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.

syzbot

unread,
Jun 12, 2023, 8:00:55 AM6/12/23
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:

HEAD commit: 7349e40704a0 Linux 5.15.116
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=112aef1d280000
kernel config: https://syzkaller.appspot.com/x/.config?x=f650a0601dbf525d
dashboard link: https://syzkaller.appspot.com/bug?extid=58e860029d947f85076a
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=102f7b1d280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1298f0d9280000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/eec1263e4f05/disk-7349e407.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/833d6ae016fd/vmlinux-7349e407.xz
kernel image: https://storage.googleapis.com/syzbot-assets/da142afba386/Image-7349e407.gz.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/6a51a32fd54e/mount_0.gz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+58e860...@syzkaller.appspotmail.com

el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:614
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
BTRFS warning (device loop0): Skipping commit of aborted transaction.
------------[ cut here ]------------
WARNING: CPU: 0 PID: 3963 at fs/btrfs/transaction.c:2011 cleanup_transaction fs/btrfs/transaction.c:2011 [inline]
WARNING: CPU: 0 PID: 3963 at fs/btrfs/transaction.c:2011 btrfs_commit_transaction+0x1e04/0x30f0 fs/btrfs/transaction.c:2519
Modules linked in:
CPU: 0 PID: 3963 Comm: syz-executor416 Not tainted 5.15.116-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/25/2023
pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : cleanup_transaction fs/btrfs/transaction.c:2011 [inline]
pc : btrfs_commit_transaction+0x1e04/0x30f0 fs/btrfs/transaction.c:2519
lr : cleanup_transaction fs/btrfs/transaction.c:2011 [inline]
lr : btrfs_commit_transaction+0x1e04/0x30f0 fs/btrfs/transaction.c:2519
sp : ffff80001ccd75a0
x29: ffff80001ccd77e0 x28: ffff0000c8441168 x27: ffff0000dba0d024
x26: 00000000fffffff4 x25: ffff0000dba0d000 x24: ffff0000ce538000
x23: ffff0000dc9400b0 x22: ffff0000dc940108 x21: ffff0000ce5399d0
x20: 0000000000000000 x19: dfff800000000000 x18: 0000000000000001
x17: ff80800008335ea8 x16: ffff80001195028c x15: ffff800008335ea8
x14: 00000000ffffffff x13: ffffffffffffffff x12: 0000000000000000
x11: ff8080000832d950 x10: 0000000000000000 x9 : 8e36bf3017668c00
x8 : 8e36bf3017668c00 x7 : 0000000000000001 x6 : 0000000000000001
x5 : ffff80001ccd6d18 x4 : ffff8000149cfca0 x3 : ffff80000854dc88
x2 : 0000000000000001 x1 : 0000000100000000 x0 : 0000000000000026
Call trace:
cleanup_transaction fs/btrfs/transaction.c:2011 [inline]
btrfs_commit_transaction+0x1e04/0x30f0 fs/btrfs/transaction.c:2519
btrfs_sync_fs+0x678/0xc94 fs/btrfs/super.c:1454
sync_filesystem+0x1a0/0x218 fs/sync.c:66
btrfs_remount+0x198/0x130c fs/btrfs/super.c:1928
legacy_reconfigure+0xfc/0x114 fs/fs_context.c:633
reconfigure_super+0x340/0x690 fs/super.c:916
do_remount fs/namespace.c:2656 [inline]
path_mount+0xc94/0x104c fs/namespace.c:3316
do_mount fs/namespace.c:3337 [inline]
__do_sys_mount fs/namespace.c:3545 [inline]
__se_sys_mount fs/namespace.c:3522 [inline]
__arm64_sys_mount+0x510/0x5e0 fs/namespace.c:3522
__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:596
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:614
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
irq event stamp: 197316
hardirqs last enabled at (197315): [<ffff80000832bae8>] __up_console_sem+0xb4/0x100 kernel/printk/printk.c:257
hardirqs last disabled at (197316): [<ffff80001194b920>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:387
softirqs last enabled at (197286): [<ffff800008020ccc>] softirq_handle_end kernel/softirq.c:401 [inline]
softirqs last enabled at (197286): [<ffff800008020ccc>] __do_softirq+0xb5c/0xe20 kernel/softirq.c:587
softirqs last disabled at (197227): [<ffff8000081b573c>] do_softirq_own_stack include/asm-generic/softirq_stack.h:10 [inline]
softirqs last disabled at (197227): [<ffff8000081b573c>] invoke_softirq kernel/softirq.c:439 [inline]
softirqs last disabled at (197227): [<ffff8000081b573c>] __irq_exit_rcu+0x28c/0x534 kernel/softirq.c:636
---[ end trace f984631084196377 ]---
BTRFS: error (device loop0) in cleanup_transaction:2011: errno=-12 Out of memory
BTRFS info (device loop0): forced readonly
BTRFS error (device loop0): Remounting read-write after error is not allowed


---
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

syzbot

unread,
Dec 22, 2023, 10:12:06 AM12/22/23
to syzkaller...@googlegroups.com
syzbot suspects this issue could be fixed by backporting the following commit:

commit 398646011e3ce53409afda64bc2024d967e83880
git tree: upstream
Author: Nikolay Borisov <nbor...@suse.com>
Date: Wed Mar 30 09:14:06 2022 +0000

btrfs: remove checks for arg argument in btrfs_ioctl_balance

bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=145f5a6ee80000
kernel config: https://syzkaller.appspot.com/x/.config?x=c431dbb457f792c5
dashboard link: https://syzkaller.appspot.com/bug?extid=58e860029d947f85076a
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15eac400e80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=166cbaf4e80000


Please keep in mind that other backports might be required as well.

For information about bisection process see: https://goo.gl/tpsmEJ#bisection
Reply all
Reply to author
Forward
0 new messages