[v6.1] WARNING in udf_new_block

0 views
Skip to first unread message

syzbot

unread,
Apr 11, 2023, 4:15:48 AM4/11/23
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 543aff194ab6 Linux 6.1.23
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=13b91ec3c80000
kernel config: https://syzkaller.appspot.com/x/.config?x=e9affea290775ea7
dashboard link: https://syzkaller.appspot.com/bug?extid=0f9361f5c663f9dd9024
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/6fe9097a8f09/disk-543aff19.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/9df5aa0f6266/vmlinux-543aff19.xz
kernel image: https://storage.googleapis.com/syzbot-assets/84127c4bde2b/bzImage-543aff19.xz

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

------------[ cut here ]------------
WARNING: CPU: 1 PID: 21140 at fs/udf/udfdecl.h:116 udf_add_free_space fs/udf/balloc.c:102 [inline]
WARNING: CPU: 1 PID: 21140 at fs/udf/udfdecl.h:116 udf_bitmap_new_block fs/udf/balloc.c:346 [inline]
WARNING: CPU: 1 PID: 21140 at fs/udf/udfdecl.h:116 udf_new_block+0x2092/0x23f0 fs/udf/balloc.c:706
Modules linked in:
CPU: 1 PID: 21140 Comm: syz-executor.1 Not tainted 6.1.23-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/30/2023
RIP: 0010:udf_updated_lvid fs/udf/udfdecl.h:114 [inline]
RIP: 0010:udf_add_free_space fs/udf/balloc.c:102 [inline]
RIP: 0010:udf_bitmap_new_block fs/udf/balloc.c:346 [inline]
RIP: 0010:udf_new_block+0x2092/0x23f0 fs/udf/balloc.c:706
Code: fe 0f 0b e9 4e fc ff ff 44 89 f1 80 e1 07 fe c1 38 c1 0f 8c d2 e0 ff ff 4c 89 f7 e8 d8 7e e6 fe e9 c5 e0 ff ff e8 ce 5e 90 fe <0f> 0b e9 13 fe ff ff 89 f9 80 e1 07 80 c1 03 38 c1 0f 8c 4e e1 ff
RSP: 0018:ffffc9000acff880 EFLAGS: 00010283
RAX: ffffffff82f92ef2 RBX: 00000000b7fd2ffa RCX: 0000000000040000
RDX: ffffc90005941000 RSI: 000000000000309d RDI: 000000000000309e
RBP: ffffc9000acffad0 R08: ffffffff82f92cff R09: ffffed1012436c3b
R10: 0000000000000000 R11: dffffc0000000001 R12: 00000000000000fe
R13: dffffc0000000000 R14: ffff88809447401c R15: 00000000000000fe
FS: 00007f95a6cfe700(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fc726132000 CR3: 000000007a621000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
udf_new_inode+0x3a3/0xf10 fs/udf/ialloc.c:86
udf_mkdir+0x10b/0xaa0 fs/udf/namei.c:674
vfs_mkdir+0x3b6/0x590 fs/namei.c:4036
do_mkdirat+0x260/0x520 fs/namei.c:4061
__do_sys_mkdir fs/namei.c:4081 [inline]
__se_sys_mkdir fs/namei.c:4079 [inline]
__x64_sys_mkdir+0x6a/0x80 fs/namei.c:4079
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f95b048c169
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:00007f95a6cfe168 EFLAGS: 00000246 ORIG_RAX: 0000000000000053
RAX: ffffffffffffffda RBX: 00007f95b05ac050 RCX: 00007f95b048c169
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 00000000200000c0
RBP: 00007f95b04e7ca1 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffecf6410bf R14: 00007f95a6cfe300 R15: 0000000000022000
</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.

syzbot

unread,
Aug 9, 2023, 4:15:53 AM8/9/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