Hello,
syzbot found the following issue on:
HEAD commit: 42616e0f09fb Linux 6.1.15
git tree: linux-6.1.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=14d687f4c80000
kernel config:
https://syzkaller.appspot.com/x/.config?x=690b9ff41783cd73
dashboard link:
https://syzkaller.appspot.com/bug?extid=a92b613efd5ee4827b35
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/db869f2ed2bd/disk-42616e0f.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/37951bbe5829/vmlinux-42616e0f.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/23aa1a75ce0f/bzImage-42616e0f.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+a92b61...@syzkaller.appspotmail.com
------------[ cut here ]------------
WARNING: CPU: 0 PID: 3676 at include/linux/backing-dev.h:246 folio_account_dirtied mm/page-writeback.c:2565 [inline]
WARNING: CPU: 0 PID: 3676 at include/linux/backing-dev.h:246 __folio_mark_dirty+0x9fd/0x1210 mm/page-writeback.c:2616
Modules linked in:
CPU: 0 PID: 3676 Comm: syz-executor.3 Not tainted 6.1.15-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
RIP: 0010:inode_to_wb include/linux/backing-dev.h:243 [inline]
RIP: 0010:folio_account_dirtied mm/page-writeback.c:2565 [inline]
RIP: 0010:__folio_mark_dirty+0x9fd/0x1210 mm/page-writeback.c:2616
Code: ff ff e8 d6 c5 d0 ff e8 99 2b 47 ff e9 81 f8 ff ff e8 c7 c5 d0 ff 4c 89 f7 48 8b 74 24 20 e8 5a ea 2d 00 eb 9c e8 b3 c5 d0 ff <0f> 0b e9 36 fb ff ff 89 d9 80 e1 07 80 c1 03 38 c1 0f 8c 96 f8 ff
RSP: 0018:ffffc9000428fa38 EFLAGS: 00010093
RAX: ffffffff81b9646d RBX: 0000000000000000 RCX: ffff88801e36d7c0
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffff888140dfc978 R08: ffffffff81b95f9d R09: ffffed10281bf930
R10: 0000000000000000 R11: dffffc0000000001 R12: 0000000000000001
R13: ffff888140dfc800 R14: ffffea0000c57dc0 R15: 1ffff110281bf92f
FS: 0000555556c47400(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b30221000 CR3: 000000004a476000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
__set_page_dirty include/linux/pagemap.h:1053 [inline]
mark_buffer_dirty+0x3e8/0x890 fs/buffer.c:1105
gfs2_unpin+0x129/0xa60 fs/gfs2/lops.c:111
buf_lo_after_commit+0x14b/0x1a0 fs/gfs2/lops.c:747
lops_after_commit fs/gfs2/lops.h:49 [inline]
gfs2_log_flush+0x1151/0x2610 fs/gfs2/log.c:1116
gfs2_kill_sb+0x50/0xd0 fs/gfs2/ops_fstype.c:1732
deactivate_locked_super+0xa0/0x110 fs/super.c:332
cleanup_mnt+0x490/0x520 fs/namespace.c:1186
task_work_run+0x246/0x300 kernel/task_work.c:179
resume_user_mode_work include/linux/resume_user_mode.h:49 [inline]
exit_to_user_mode_loop+0xd9/0x100 kernel/entry/common.c:171
exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:203
__syscall_exit_to_user_mode_work kernel/entry/common.c:285 [inline]
syscall_exit_to_user_mode+0x60/0x2c0 kernel/entry/common.c:296
do_syscall_64+0x49/0xb0 arch/x86/entry/common.c:86
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7fda4688d567
Code: ff ff ff f7 d8 64 89 01 48 83 c8 ff c3 66 0f 1f 44 00 00 31 f6 e9 09 00 00 00 66 0f 1f 84 00 00 00 00 00 b8 a6 00 00 00 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:00007ffdf6414858 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 00007fda4688d567
RDX: 00007ffdf641492b RSI: 000000000000000a RDI: 00007ffdf6414920
RBP: 00007ffdf6414920 R08: 00000000ffffffff R09: 00007ffdf64146f0
R10: 0000555556c488b3 R11: 0000000000000246 R12: 00007fda468e6b24
R13: 00007ffdf64159e0 R14: 0000555556c48810 R15: 00007ffdf6415a20
</TASK>
---
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.