Hello,
syzbot found the following issue on:
HEAD commit: 6449a0ba6843 Linux 6.1.19
git tree: linux-6.1.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=171a92dcc80000
kernel config:
https://syzkaller.appspot.com/x/.config?x=9ed8b3ec03e8c126
dashboard link:
https://syzkaller.appspot.com/bug?extid=9f01f4e38d051c1b0cff
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/0ad616da3180/disk-6449a0ba.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/42677a30acb3/vmlinux-6449a0ba.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/2e21fe35d03d/bzImage-6449a0ba.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+9f01f4...@syzkaller.appspotmail.com
------------[ cut here ]------------
WARNING: CPU: 1 PID: 3651 at fs/buffer.c:1081 mark_buffer_dirty+0x47b/0x8b0
Modules linked in:
CPU: 1 PID: 3651 Comm: syz-executor.0 Not tainted 6.1.19-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
RIP: 0010:mark_buffer_dirty+0x47b/0x8b0 fs/buffer.c:1081
Code: c7 e0 c3 f9 8a be 3f 00 00 00 48 c7 c2 20 c4 f9 8a e8 69 f3 6a ff e9 e2 fc ff ff e8 ff b5 8a ff e9 e0 fe ff ff e8 f5 b5 8a ff <0f> 0b e9 cc fb ff ff e8 e9 b5 8a ff 0f 0b e9 0f fc ff ff e8 dd b5
RSP: 0018:ffffc9000449f8a8 EFLAGS: 00010293
RAX: ffffffff81ffab2b RBX: ffff88804c18f401 RCX: ffff888076538000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000000000000 R08: ffffffff81ffa6f1 R09: ffffed1009871b97
R10: 0000000000000000 R11: dffffc0000000001 R12: 0000000000000007
R13: dffffc0000000000 R14: ffffc9000449f920 R15: ffff88804c38dcb0
FS: 0000555556a40400(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fa5749b75a8 CR3: 000000005333d000 CR4: 00000000003506e0
Call Trace:
<TASK>
__nilfs_mark_inode_dirty+0x101/0x280 fs/nilfs2/inode.c:1097
nilfs_mark_inode_dirty fs/nilfs2/nilfs.h:288 [inline]
nilfs_evict_inode+0x185/0x420 fs/nilfs2/inode.c:934
evict+0x2a4/0x620 fs/inode.c:664
__dentry_kill+0x436/0x650 fs/dcache.c:607
shrink_dentry_list+0x398/0x6a0 fs/dcache.c:1201
shrink_dcache_parent+0xc9/0x480
do_one_tree+0x23/0xe0 fs/dcache.c:1682
shrink_dcache_for_umount+0x79/0x120 fs/dcache.c:1699
generic_shutdown_super+0x63/0x340 fs/super.c:473
kill_block_super+0x7a/0xe0 fs/super.c:1441
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/0x2d0 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:0x7fb01808d567
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:00007ffd4a076f58 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 00007fb01808d567
RDX: 00007ffd4a07702c RSI: 000000000000000a RDI: 00007ffd4a077020
RBP: 00007ffd4a077020 R08: 00000000ffffffff R09: 00007ffd4a076df0
R10: 0000555556a418b3 R11: 0000000000000246 R12: 00007fb0180e6b24
R13: 00007ffd4a0780e0 R14: 0000555556a41810 R15: 00007ffd4a078120
</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.