Hello,
syzbot found the following issue on:
HEAD commit: 3036cd0d3328 Merge tag 'ata-7.0-final' of git://git.kernel..
git tree: upstream
console output:
https://syzkaller.appspot.com/x/log.txt?x=13b49e06580000
kernel config:
https://syzkaller.appspot.com/x/.config?x=d46eab0cfd31c214
dashboard link:
https://syzkaller.appspot.com/bug?extid=c4a3f3309f242c420850
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
CC: [
linux-...@vger.kernel.org linux-...@vger.kernel.org]
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image (non-bootable):
https://storage.googleapis.com/syzbot-assets/d900f083ada3/non_bootable_disk-3036cd0d.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/52b4694b61e7/vmlinux-3036cd0d.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/3cae4a12f2ba/bzImage-3036cd0d.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+c4a3f3...@syzkaller.appspotmail.com
------------[ cut here ]------------
!buffer_uptodate(bh)
WARNING: fs/buffer.c:1180 at mark_buffer_dirty+0x299/0x440 fs/buffer.c:1180, CPU#0: syz.0.0/5346
Modules linked in:
CPU: 0 UID: 0 PID: 5346 Comm: syz.0.0 Not tainted syzkaller #0 PREEMPT(full)
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
RIP: 0010:mark_buffer_dirty+0x299/0x440 fs/buffer.c:1180
Code: 4c 89 f7 e8 e9 fc d9 ff 49 8b 3e be 40 00 00 00 5b 41 5c 41 5e 41 5f 5d e9 c4 60 fb ff e8 7f 1c 6e ff eb 8c e8 78 1c 6e ff 90 <0f> 0b 90 e9 a5 fd ff ff e8 6a 1c 6e ff 90 0f 0b 90 e9 cf fd ff ff
RSP: 0018:ffffc9000d9571b0 EFLAGS: 00010287
RAX: ffffffff8257b2f8 RBX: ffff888047956d98 RCX: 0000000000100000
RDX: ffffc900209c2000 RSI: 00000000000025c4 RDI: 00000000000025c5
RBP: ffffc9000d957301 R08: ffff888047956d9f R09: 1ffff11008f2adb3
R10: dffffc0000000000 R11: ffffed1008f2adb4 R12: ffff888011ee69dc
R13: 1ffff110023dcd38 R14: ffff888011ee69c0 R15: 0000000000000017
FS: 00007f33604526c0(0000) GS:ffff88808ca49000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f7102b958f5 CR3: 000000001a9f2000 CR4: 0000000000352ef0
Call Trace:
<TASK>
free_data fs/minix/itree_common.c:271 [inline]
truncate fs/minix/itree_common.c:320 [inline]
V2_minix_truncate+0x2ee/0x1160 fs/minix/itree_v2.c:69
minix_truncate fs/minix/inode.c:729 [inline]
minix_evict_inode+0x1d1/0x260 fs/minix/inode.c:50
evict+0x61e/0xb10 fs/inode.c:846
minix_mkdir+0xe2/0x120 fs/minix/namei.c:136
vfs_mkdir+0x413/0x630 fs/namei.c:5239
ovl_do_mkdir fs/overlayfs/overlayfs.h:257 [inline]
ovl_workdir_create+0x4d7/0x940 fs/overlayfs/super.c:345
ovl_make_workdir fs/overlayfs/super.c:682 [inline]
ovl_get_workdir fs/overlayfs/super.c:840 [inline]
ovl_fill_super_creds fs/overlayfs/super.c:1453 [inline]
ovl_fill_super+0x1a56/0x5e40 fs/overlayfs/super.c:1564
vfs_get_super fs/super.c:1327 [inline]
get_tree_nodev+0xbb/0x150 fs/super.c:1346
vfs_get_tree+0x92/0x2a0 fs/super.c:1754
fc_mount fs/namespace.c:1193 [inline]
do_new_mount_fc fs/namespace.c:3763 [inline]
do_new_mount+0x341/0xd30 fs/namespace.c:3839
do_mount fs/namespace.c:4172 [inline]
__do_sys_mount fs/namespace.c:4361 [inline]
__se_sys_mount+0x31d/0x420 fs/namespace.c:4338
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0x14d/0xf80 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f335f59c819
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 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 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f3360451fe8 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007f335f816180 RCX: 00007f335f59c819
RDX: 0000200000000b80 RSI: 0000200000000100 RDI: 0000000000000000
RBP: 00007f335f632c91 R08: 0000200000000140 R09: 0000000000000000
R10: 0000000000004008 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f335f816218 R14: 00007f335f816180 R15: 00007ffdedb1d308
</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.
If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup