[syzbot] [udf?] WARNING in udf_open_lvid

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 6916d5703ddf Merge tag 'drm-fixes-2026-05-16' of https://g..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=16738596580000
kernel config: https://syzkaller.appspot.com/x/.config?x=7f195f6be48c12ec
dashboard link: https://syzkaller.appspot.com/bug?extid=0306b38d9ed6ef71467d
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 (non-bootable): https://storage.googleapis.com/syzbot-assets/d900f083ada3/non_bootable_disk-6916d570.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/8bed404c07b1/vmlinux-6916d570.xz
kernel image: https://storage.googleapis.com/syzbot-assets/d4742556e816/bzImage-6916d570.xz

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

loop0: detected capacity change from 0 to 2048
UDF-fs: INFO Mounting volume 'Li uxUDF', timestamp 2022/11/22 14:59 (1000)
loop0: detected capacity change from 2048 to 0
=======================================================
WARNING: The mand mount option has been deprecated and
and is ignored by this kernel. Remove the mand
option from the mount to silence this warning.
=======================================================
------------[ cut here ]------------
!buffer_uptodate(bh)
WARNING: fs/buffer.c:1087 at mark_buffer_dirty+0x299/0x410 fs/buffer.c:1087, CPU#0: syz.0.0/5328
Modules linked in:
CPU: 0 UID: 0 PID: 5328 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/0x410 fs/buffer.c:1087
Code: 4c 89 f7 e8 b9 5c da ff 49 8b 3e be 40 00 00 00 5b 41 5c 41 5e 41 5f 5d e9 b4 63 fb ff e8 bf 90 6d ff eb 8c e8 b8 90 6d ff 90 <0f> 0b 90 e9 a5 fd ff ff e8 aa 90 6d ff 90 0f 0b 90 e9 cf fd ff ff
RSP: 0018:ffffc9000da17b90 EFLAGS: 00010293
RAX: ffffffff82584318 RBX: ffff888047950828 RCX: ffff888012690000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000002
RBP: ffffc9000da17c01 R08: ffff88804795082f R09: 1ffff11008f2a105
R10: dffffc0000000000 R11: ffffed1008f2a106 R12: ffff888050a4c009
R13: 1ffff92001b42f80 R14: dffffc0000000000 R15: ffff888047950828
FS: 00007efcfaa656c0(0000) GS:ffff88808c87f000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffcca852c04 CR3: 0000000012501000 CR4: 0000000000352ef0
Call Trace:
<TASK>
udf_open_lvid+0x38a/0x5d0 fs/udf/super.c:2078
udf_reconfigure+0x336/0x540 fs/udf/super.c:679
reconfigure_super+0x227/0x8a0 fs/super.c:1080
do_remount fs/namespace.c:3400 [inline]
path_mount+0xdc5/0x10e0 fs/namespace.c:4146
do_mount fs/namespace.c:4167 [inline]
__do_sys_mount fs/namespace.c:4383 [inline]
__se_sys_mount+0x31d/0x420 fs/namespace.c:4360
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0x15f/0xf80 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7efcf9b9e0ca
Code: 48 c7 c2 e8 ff ff ff f7 d8 64 89 02 b8 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 49 89 ca b8 a5 00 00 00 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:00007efcfaa64e18 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007efcfaa64ea0 RCX: 00007efcf9b9e0ca
RDX: 0000200000000180 RSI: 0000200000000100 RDI: 0000000000000000
RBP: 0000200000000180 R08: 00007efcfaa64ea0 R09: 0000000001e4047c
R10: 0000000001e4047c R11: 0000000000000246 R12: 0000200000000100
R13: 00007efcfaa64e60 R14: 0000000000000000 R15: 0000200000000ec0
</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