WARNING in btrfs_commit_transaction (2)

4 views
Skip to first unread message

syzbot

unread,
Dec 9, 2022, 5:50:39 AM12/9/22
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 3f8a27f9e27b Linux 4.19.211
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=17ccfb37880000
kernel config: https://syzkaller.appspot.com/x/.config?x=9b9277b418617afe
dashboard link: https://syzkaller.appspot.com/bug?extid=165a6160d239b95123d7
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/98c0bdb4abb3/disk-3f8a27f9.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/ea228ff02669/vmlinux-3f8a27f9.xz

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

alloc_file_pseudo+0x165/0x250 fs/file_table.c:231
__shmem_file_setup.part.0+0x102/0x2b0 mm/shmem.c:3976
------------[ cut here ]------------
__shmem_file_setup mm/shmem.c:3959 [inline]
shmem_file_setup+0x61/0x90 mm/shmem.c:4006
__do_sys_memfd_create mm/memfd.c:325 [inline]
__se_sys_memfd_create+0x26b/0x440 mm/memfd.c:268
WARNING: CPU: 1 PID: 26023 at fs/fs-writeback.c:2370 __writeback_inodes_sb_nr.cold+0x11/0x18 fs/fs-writeback.c:2370
Kernel panic - not syncing: panic_on_warn set ...

do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x7ffa62f550d9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 19 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffa614c6f38 EFLAGS: 00000202 ORIG_RAX: 000000000000013f
RAX: ffffffffffffffda RBX: 00000000000050ef RCX: 00007ffa62f550d9
RDX: 00007ffa614c6fdc RSI: 0000000000000000 RDI: 00007ffa62fafe81
RBP: 00000000000050ef R08: 00007ffa614c6e20 R09: ffffffffffffffff
R10: 0000000000000000 R11: 0000000000000202 R12: 0000000020005100
R13: 00007ffa614c6fdc R14: 00007ffa614c6fe0 R15: 0000000020005140
CPU: 1 PID: 26023 Comm: btrfs-transacti Not tainted 4.19.211-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x1fc/0x2ef lib/dump_stack.c:118
panic+0x26a/0x50e kernel/panic.c:186
__warn.cold+0x20/0x5a kernel/panic.c:541
report_bug+0x262/0x2b0 lib/bug.c:183
fixup_bug arch/x86/kernel/traps.c:178 [inline]
fixup_bug arch/x86/kernel/traps.c:173 [inline]
do_error_trap+0x1d7/0x310 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:2370
Code: e1 e8 36 ba 6d f9 48 c7 c7 c0 f9 74 88 e8 95 eb fe ff 0f 0b e9 75 12 b9 f9 e8 1e ba 6d f9 48 c7 c7 c0 f9 74 88 e8 7d eb fe ff <0f> 0b e9 c9 34 b9 f9 e8 06 ba 6d f9 48 c7 c7 c0 f9 74 88 e8 65 eb
RSP: 0018:ffff88804bf27c48 EFLAGS: 00010286
RAX: 0000000000000024 RBX: 1ffff110097e4f8b RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff814dff01 RDI: ffffed10097e4f7b
RBP: ffff8880af9b4140 R08: 0000000000000024 R09: 0000000000000000
R10: 0000000000000005 R11: 0000000000000000 R12: 0000000000006400
R13: ffff88804c499580 R14: ffff8880af9b4270 R15: ffff88804bf27c88
btrfs_start_delalloc_flush fs/btrfs/transaction.c:1927 [inline]
btrfs_commit_transaction+0x1bb1/0x2480 fs/btrfs/transaction.c:2078
transaction_kthread+0x385/0x490 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

unread,
Apr 8, 2023, 6:50:26 AM4/8/23
to syzkaller...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages