From: syzbot <syzbot+de2fef01040748da6822@syzkaller.appspotmail.com>
To: golasch18@web.de, jack@suse.com, jack@suse.cz,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [udf?] WARNING in udf_map_block
Date: Mon, 26 Oct 2026 23:16:42 -0700 [thread overview]
Message-ID: <6ae041ca.6200f071.51519.0f36.GAE@google.com> (raw)
In-Reply-To: <6a81cb33.9ebadd4d.20b15e.0018.GAE@google.com>
syzbot has found a reproducer for the following issue on:
HEAD commit: d135ab453a74 Merge tag 'backlight-next-7.4' of git://git.k..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=13dadee1580000
kernel config: https://syzkaller.appspot.com/x/.config?x=b990d88b41ee3220
dashboard link: https://syzkaller.appspot.com/bug?extid=de2fef01040748da6822
compiler: Debian clang version 22.1.8 (1~deb13u4), Debian LLD 22.1.8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16c93721580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16146469580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/7442602f534e/disk-d135ab45.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/ddc5d8dd9280/vmlinux-d135ab45.xz
kernel image: https://storage.googleapis.com/syzbot-assets/ec40039f5ff5/bzImage-d135ab45.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/2af222d62d5c/mount_0.gz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+de2fef01040748da6822@syzkaller.appspotmail.com
------------[ cut here ]------------
iinfo->i_alloc_type == ICBTAG_FLAG_AD_IN_ICB
WARNING: fs/udf/inode.c:355 at udf_map_block+0x387f/0x4240 fs/udf/inode.c:355, CPU#0: syz.1.25/6056
Modules linked in:
CPU: 0 UID: 0 PID: 6056 Comm: syz.1.25 Not tainted syzkaller #0 PREEMPT_{RT,(full)}
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/07/2026
RIP: 0010:udf_map_block+0x387f/0x4240 fs/udf/inode.c:355
Code: af 78 66 10 48 3b 84 24 40 03 00 00 75 49 89 d8 48 8d 65 d8 5b 41 5c 41 5d 41 5e 41 5f 5d e9 48 c2 0b 08 cc e8 f2 6e 5f fe 90 <0f> 0b 90 bb 8b ff ff ff 4c 8b 74 24 78 eb aa 44 89 f9 80 e1 07 80
RSP: 0018:ffffc900048b6fc0 EFLAGS: 00010293
RAX: ffffffff8368679e RBX: 0000000000000003 RCX: ffff888022703e80
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffc900048b7350 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000100 R11: ffffffff83687170 R12: ffffc900048b7368
R13: ffff88804a8a09a8 R14: dffffc0000000000 R15: ffff88804a8a07c8
FS: 00007fee297756c0(0000) GS:ffff888124732000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f0274e99440 CR3: 000000002c070000 CR4: 00000000003526f0
Call Trace:
<TASK>
__udf_get_block+0x52/0x250 fs/udf/inode.c:476
get_more_blocks fs/direct-io.c:644 [inline]
do_direct_IO fs/direct-io.c:932 [inline]
__blockdev_direct_IO+0x1965/0x33d0 fs/direct-io.c:1236
blockdev_direct_IO include/linux/fs.h:3160 [inline]
udf_direct_IO+0x13b/0x210 fs/udf/inode.c:309
generic_file_read_iter+0x346/0x560 mm/filemap.c:3011
copy_splice_read+0x605/0xab0 fs/splice.c:362
do_splice_read fs/splice.c:979 [inline]
splice_direct_to_actor+0x4c1/0xcc0 fs/splice.c:1077
do_splice_direct_actor fs/splice.c:1230 [inline]
do_splice_direct+0x19b/0x2a0 fs/splice.c:1256
do_sendfile+0x540/0x7e0 fs/read_write.c:1371
__do_sys_sendfile64 fs/read_write.c:1432 [inline]
__se_sys_sendfile64+0x144/0x1a0 fs/read_write.c:1418
do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
do_syscall_64+0x166/0x520 arch/x86/entry/syscall_64.c:84
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fee2a13f559
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:00007fee29775028 EFLAGS: 00000246 ORIG_RAX: 0000000000000028
RAX: ffffffffffffffda RBX: 00007fee2a3c6090 RCX: 00007fee2a13f559
RDX: 0000000000000000 RSI: 0000000000000004 RDI: 0000000000000004
RBP: 00007fee2a1d6b20 R08: 0000000000000000 R09: 0000000000000000
R10: 000000000e3aa6ea R11: 0000000000000246 R12: 0000000000000000
R13: 00007fee2a3c6128 R14: 00007fee2a3c6090 R15: 00007fff0dc92f08
</TASK>
---
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.
next prev parent reply other threads:[~2026-10-27 6:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-16 14:37 syzbot
2026-10-27 6:16 ` syzbot [this message]
2026-10-27 15:56 ` syzbot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6ae041ca.6200f071.51519.0f36.GAE@google.com \
--to=syzbot+de2fef01040748da6822@syzkaller.appspotmail.com \
--cc=golasch18@web.de \
--cc=jack@suse.com \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®