[syzbot] [block?] WARNING in blk_revalidate_disk_zones

Hello,

syzbot found the following issue on:

HEAD commit:    d58772d8520c Merge tag 'regmap-fix-v7.2-rc7' of git://git...
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=160ad132580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=c44651ea7dd2f307
dashboard link: https://syzkaller.appspot.com/bug?extid=643a6dd130546afdf1fb
compiler:       gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/cef626cbb901/disk-d58772d8.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/99faa1c91124/vmlinux-d58772d8.xz
kernel image: https://storage.googleapis.com/syzbot-assets/cf8806baff68/bzImage-d58772d8.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: [email protected]

null_blk: nullb1: using native zone append
------------[ cut here ]------------
!blk_queue_is_zoned(q)
WARNING: block/blk-zoned.c:2357 at blk_revalidate_disk_zones+0x962/0xce0 block/blk-zoned.c:2357, CPU#1: syz.4.694/8600
Modules linked in:
CPU: 1 UID: 0 PID: 8600 Comm: syz.4.694 Tainted: G             L      syzkaller #0 PREEMPT(full) 
Tainted: [L]=SOFTLOCKUP
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/16/2026
RIP: 0010:blk_revalidate_disk_zones+0x962/0xce0 block/blk-zoned.c:2357
Code: e8 73 15 fc fc 49 81 fe 00 f0 ff ff 0f 87 00 02 00 00 e8 c1 1a fc fc 4c 89 f7 e8 c9 c2 c9 fc e9 ce fa ff ff e8 af 1a fc fc 90 <0f> 0b 90 41 be fb ff ff ff e9 d5 fb ff ff e8 2b a9 6c fd e9 5c f7
RSP: 0018:ffffc9000388f918 EFLAGS: 00010287
RAX: 0000000000004d06 RBX: ffff88804bda7000 RCX: ffffc900063c1000
RDX: 0000000000080000 RSI: ffffffff850e58d1 RDI: ffff888079178000
RBP: 0000000000000000 R08: 0000000000000005 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000001 R12: ffff88802b726670
R13: 0000000000000000 R14: ffff88807e08e018 R15: ffff88804bda7090
FS:  00007f108a7486c0(0000) GS:ffff888123eec000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fd5511556c8 CR3: 0000000056586000 CR4: 00000000003526f0
DR0: ffffffffffffffff DR1: 00000000000001f8 DR2: 0000000000000083
DR3: ffffffffefffff15 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 null_add_dev+0x125f/0x1df0 drivers/block/null_blk/main.c:2047
 nullb_device_power_store+0x29d/0x350 drivers/block/null_blk/main.c:501
 flush_write_buffer fs/configfs/file.c:207 [inline]
 configfs_write_iter+0x302/0x4e0 fs/configfs/file.c:229
 new_sync_write fs/read_write.c:595 [inline]
 vfs_write+0x6ac/0x1050 fs/read_write.c:687
 ksys_write+0x12a/0x250 fs/read_write.c:739
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0x115/0x870 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f108979e0d9
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:00007f108a748028 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007f1089a25fa0 RCX: 00007f108979e0d9
RDX: 0000000000000002 RSI: 0000200000000700 RDI: 0000000000000005
RBP: 00007f1089835024 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f1089a26038 R14: 00007f1089a25fa0 R15: 00007ffc5551d348
 </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 [email protected].

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