[v5.15] WARNING in udf_free_inode (4)

0 views
Skip to first unread message

syzbot

unread,
7:10 AM (10 hours ago) 7:10 AM
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 241d66fa280c Linux 5.15.208
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=17f73a0e580000
kernel config: https://syzkaller.appspot.com/x/.config?x=353ae28c40b35af5
dashboard link: https://syzkaller.appspot.com/bug?extid=765c087b175b0b0de5dc
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/d3e9d10633a1/disk-241d66fa.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/beca1f713e4b/vmlinux-241d66fa.xz
kernel image: https://storage.googleapis.com/syzbot-assets/26a15a6e1c14/bzImage-241d66fa.xz

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

------------[ cut here ]------------
WARNING: CPU: 1 PID: 5120 at fs/udf/udfdecl.h:127 udf_updated_lvid fs/udf/udfdecl.h:125 [inline]
WARNING: CPU: 1 PID: 5120 at fs/udf/udfdecl.h:127 udf_free_inode+0x21c/0x2d0 fs/udf/ialloc.c:41
Modules linked in:
CPU: 1 PID: 5120 Comm: syz.0.201 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/18/2026
RIP: 0010:udf_updated_lvid fs/udf/udfdecl.h:125 [inline]
RIP: 0010:udf_free_inode+0x21c/0x2d0 fs/udf/ialloc.c:41
Code: ff ff 4c 89 f7 31 f6 48 89 da 31 c9 41 b8 01 00 00 00 48 83 c4 18 5b 41 5c 41 5d 41 5e 41 5f 5d e9 29 90 ff ff e8 c4 f4 b1 fe <0f> 0b e9 74 ff ff ff 89 d9 80 e1 07 fe c1 38 c1 0f 8c 72 fe ff ff
RSP: 0018:ffffc9000396fc50 EFLAGS: 00010283
RAX: ffffffff82c7414c RBX: ffff888061a5ae30 RCX: 0000000000080000
RDX: ffffc9000d3d9000 RSI: 00000000000105bb RDI: 00000000000105bc
RBP: 0000000055555555 R08: ffffc9000396fa27 R09: 1ffff9200072df44
R10: dffffc0000000000 R11: fffff5200072df45 R12: 1ffff1100c27bccf
R13: ffff88805a54901c R14: dffffc0000000000 R15: ffff8880613de678
FS: 00007f3bc7f266c0(0000) GS:ffff8880b9100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f3bc7f25ff8 CR3: 0000000058c95000 CR4: 00000000003526e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
evict+0x4c9/0x8d0 fs/inode.c:647
do_unlinkat+0x3e7/0x710 fs/namei.c:4363
__do_sys_unlinkat fs/namei.c:4399 [inline]
__se_sys_unlinkat fs/namei.c:4392 [inline]
__x64_sys_unlinkat+0xd1/0xe0 fs/namei.c:4392
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f3bc9cede59
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:00007f3bc7f26028 EFLAGS: 00000246 ORIG_RAX: 0000000000000107
RAX: ffffffffffffffda RBX: 00007f3bc9f67090 RCX: 00007f3bc9cede59
RDX: 0000000000000000 RSI: 0000200000000380 RDI: ffffffffffffff9c
RBP: 00007f3bc9d83d6f R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f3bc9f67128 R14: 00007f3bc9f67090 R15: 00007ffecb498b38
</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
Reply all
Reply to author
Forward
0 new messages