WARNING in __writeback_inodes_sb_nr
10 views
Skip to first unread message
syzbot
Sep 20, 2020, 10:27:16 AM9/20/20
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: 015e94d0 Linux 4.19.146
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=10ce6009900000
kernel config: https://syzkaller.appspot.com/x/.config?x=243dd74ad58a8a57
dashboard link: https://syzkaller.appspot.com/bug?extid=5c2dc141988585eb49ce
compiler: gcc (GCC) 10.1.0-syz 20200507
Unfortunately, I don't have any reproducer for this issue yet.
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+5c2dc1...@syzkaller.appspotmail.com
BTRFS info (device loop3): checking UUID tree
------------[ cut here ]------------
WARNING: CPU: 0 PID: 9992 at fs/fs-writeback.c:2394 __writeback_inodes_sb_nr.cold+0x11/0x18 fs/fs-writeback.c:2394
Kernel panic - not syncing: panic_on_warn set ...
CPU: 0 PID: 9992 Comm: btrfs-transacti Not tainted 4.19.146-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x22c/0x33e lib/dump_stack.c:118
panic+0x2ac/0x565 kernel/panic.c:186
__warn.cold+0x20/0x5a kernel/panic.c:541
report_bug+0x262/0x2b0 lib/bug.c:186
fixup_bug arch/x86/kernel/traps.c:178 [inline]
fixup_bug arch/x86/kernel/traps.c:173 [inline]
do_error_trap+0x1e1/0x330 arch/x86/kernel/traps.c:296
invalid_op+0x14/0x20 arch/x86/entry/entry_64.S:1038
RIP: 0010:__writeback_inodes_sb_nr.cold+0x11/0x18 fs/fs-writeback.c:2394
Code: 19 d8 af ff 41 0f b6 f5 48 c7 c7 80 f3 94 89 e8 39 05 f4 01 e9 e3 7b ff ff e8 ff d7 af ff 48 c7 c7 e0 5c 16 88 e8 22 53 99 ff <0f> 0b e9 9a 80 ff ff e8 e7 d7 af ff 0f b6 f3 48 c7 c7 00 f4 94 89
RSP: 0018:ffff88805052fc48 EFLAGS: 00010286
RAX: 0000000000000024 RBX: 1ffff1100a0a5f8b RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff815b523f RDI: ffffed100a0a5f7b
RBP: ffff8880823fcdc0 R08: 0000000000000024 R09: 0000000000000000
R10: 0000000000000005 R11: 0000000000000000 R12: 0000000000006400
R13: ffff88808f654e40 R14: ffff8880823fcef0 R15: ffff88805052fc88
btrfs_start_delalloc_flush fs/btrfs/transaction.c:1924 [inline]
btrfs_commit_transaction+0x1bb1/0x24a0 fs/btrfs/transaction.c:2075
transaction_kthread+0x385/0x483 fs/btrfs/disk-io.c:1794
kthread+0x33f/0x460 kernel/kthread.c:259
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415
Kernel Offset: disabled
Rebooting in 86400 seconds..
---
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 found the following issue on:
HEAD commit: 015e94d0 Linux 4.19.146
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=10ce6009900000
kernel config: https://syzkaller.appspot.com/x/.config?x=243dd74ad58a8a57
dashboard link: https://syzkaller.appspot.com/bug?extid=5c2dc141988585eb49ce
compiler: gcc (GCC) 10.1.0-syz 20200507
Unfortunately, I don't have any reproducer for this issue yet.
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+5c2dc1...@syzkaller.appspotmail.com
BTRFS info (device loop3): checking UUID tree
------------[ cut here ]------------
WARNING: CPU: 0 PID: 9992 at fs/fs-writeback.c:2394 __writeback_inodes_sb_nr.cold+0x11/0x18 fs/fs-writeback.c:2394
Kernel panic - not syncing: panic_on_warn set ...
CPU: 0 PID: 9992 Comm: btrfs-transacti Not tainted 4.19.146-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x22c/0x33e lib/dump_stack.c:118
panic+0x2ac/0x565 kernel/panic.c:186
__warn.cold+0x20/0x5a kernel/panic.c:541
report_bug+0x262/0x2b0 lib/bug.c:186
fixup_bug arch/x86/kernel/traps.c:178 [inline]
fixup_bug arch/x86/kernel/traps.c:173 [inline]
do_error_trap+0x1e1/0x330 arch/x86/kernel/traps.c:296
invalid_op+0x14/0x20 arch/x86/entry/entry_64.S:1038
RIP: 0010:__writeback_inodes_sb_nr.cold+0x11/0x18 fs/fs-writeback.c:2394
Code: 19 d8 af ff 41 0f b6 f5 48 c7 c7 80 f3 94 89 e8 39 05 f4 01 e9 e3 7b ff ff e8 ff d7 af ff 48 c7 c7 e0 5c 16 88 e8 22 53 99 ff <0f> 0b e9 9a 80 ff ff e8 e7 d7 af ff 0f b6 f3 48 c7 c7 00 f4 94 89
RSP: 0018:ffff88805052fc48 EFLAGS: 00010286
RAX: 0000000000000024 RBX: 1ffff1100a0a5f8b RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff815b523f RDI: ffffed100a0a5f7b
RBP: ffff8880823fcdc0 R08: 0000000000000024 R09: 0000000000000000
R10: 0000000000000005 R11: 0000000000000000 R12: 0000000000006400
R13: ffff88808f654e40 R14: ffff8880823fcef0 R15: ffff88805052fc88
btrfs_start_delalloc_flush fs/btrfs/transaction.c:1924 [inline]
btrfs_commit_transaction+0x1bb1/0x24a0 fs/btrfs/transaction.c:2075
transaction_kthread+0x385/0x483 fs/btrfs/disk-io.c:1794
kthread+0x33f/0x460 kernel/kthread.c:259
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415
Kernel Offset: disabled
Rebooting in 86400 seconds..
---
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
Sep 20, 2020, 1:14:17 PM9/20/20
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:
HEAD commit: 015e94d0 Linux 4.19.146
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=15aad009900000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14134365900000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+5c2dc1...@syzkaller.appspotmail.com
BTRFS info (device loop0): turning on flush-on-commit
BTRFS info (device loop0): disk space caching is enabled
BTRFS info (device loop0): has skinny extents
BTRFS info (device loop0): checking UUID tree
------------[ cut here ]------------
WARNING: CPU: 0 PID: 6640 at fs/fs-writeback.c:2394 __writeback_inodes_sb_nr.cold+0x11/0x18 fs/fs-writeback.c:2394
RAX: 0000000000000024 RBX: 1ffff11013f1df8b RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff815b523f RDI: ffffed1013f1df7b
RBP: ffff8880a44de240 R08: 0000000000000024 R09: 0000000000000000
HEAD commit: 015e94d0 Linux 4.19.146
git tree: linux-4.19.y
kernel config: https://syzkaller.appspot.com/x/.config?x=243dd74ad58a8a57
dashboard link: https://syzkaller.appspot.com/bug?extid=5c2dc141988585eb49ce
compiler: gcc (GCC) 10.1.0-syz 20200507
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15a1184b900000
dashboard link: https://syzkaller.appspot.com/bug?extid=5c2dc141988585eb49ce
compiler: gcc (GCC) 10.1.0-syz 20200507
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14134365900000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+5c2dc1...@syzkaller.appspotmail.com
BTRFS info (device loop0): disk space caching is enabled
BTRFS info (device loop0): has skinny extents
BTRFS info (device loop0): checking UUID tree
------------[ cut here ]------------
WARNING: CPU: 0 PID: 6640 at fs/fs-writeback.c:2394 __writeback_inodes_sb_nr.cold+0x11/0x18 fs/fs-writeback.c:2394
Kernel panic - not syncing: panic_on_warn set ...
CPU: 0 PID: 6640 Comm: btrfs-transacti Not tainted 4.19.146-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x22c/0x33e lib/dump_stack.c:118
panic+0x2ac/0x565 kernel/panic.c:186
__warn.cold+0x20/0x5a kernel/panic.c:541
report_bug+0x262/0x2b0 lib/bug.c:186
fixup_bug arch/x86/kernel/traps.c:178 [inline]
fixup_bug arch/x86/kernel/traps.c:173 [inline]
do_error_trap+0x1e1/0x330 arch/x86/kernel/traps.c:296
invalid_op+0x14/0x20 arch/x86/entry/entry_64.S:1038
RIP: 0010:__writeback_inodes_sb_nr.cold+0x11/0x18 fs/fs-writeback.c:2394
Code: 19 d8 af ff 41 0f b6 f5 48 c7 c7 80 f3 94 89 e8 39 05 f4 01 e9 e3 7b ff ff e8 ff d7 af ff 48 c7 c7 e0 5c 16 88 e8 22 53 99 ff <0f> 0b e9 9a 80 ff ff e8 e7 d7 af ff 0f b6 f3 48 c7 c7 00 f4 94 89
RSP: 0018:ffff88809f8efc48 EFLAGS: 00010286
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x22c/0x33e lib/dump_stack.c:118
panic+0x2ac/0x565 kernel/panic.c:186
__warn.cold+0x20/0x5a kernel/panic.c:541
report_bug+0x262/0x2b0 lib/bug.c:186
fixup_bug arch/x86/kernel/traps.c:178 [inline]
fixup_bug arch/x86/kernel/traps.c:173 [inline]
do_error_trap+0x1e1/0x330 arch/x86/kernel/traps.c:296
invalid_op+0x14/0x20 arch/x86/entry/entry_64.S:1038
RIP: 0010:__writeback_inodes_sb_nr.cold+0x11/0x18 fs/fs-writeback.c:2394
Code: 19 d8 af ff 41 0f b6 f5 48 c7 c7 80 f3 94 89 e8 39 05 f4 01 e9 e3 7b ff ff e8 ff d7 af ff 48 c7 c7 e0 5c 16 88 e8 22 53 99 ff <0f> 0b e9 9a 80 ff ff e8 e7 d7 af ff 0f b6 f3 48 c7 c7 00 f4 94 89
RAX: 0000000000000024 RBX: 1ffff11013f1df8b RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff815b523f RDI: ffffed1013f1df7b
RBP: ffff8880a44de240 R08: 0000000000000024 R09: 0000000000000000
R10: 0000000000000005 R11: 0000000000000000 R12: 0000000000006400
R13: ffff8880a08f7480 R14: ffff8880a44de370 R15: ffff88809f8efc88
Reply all
Reply to author
Forward
0 new messages