From: syzbot <syzbot+7f04e5b3fea8b6c33d39@syzkaller.appspotmail.com>
To: asml.silence@gmail.com, axboe@kernel.dk,
io-uring@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] [io-uring?] WARNING in vmap_small_pages_range_noflush
Date: Mon, 11 Aug 2025 10:54:27 -0700 [thread overview]
Message-ID: <689a2e53.050a0220.51d73.00a1.GAE@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 6e64f4580381 Merge tag 'input-for-v6.17-rc0' of git://git...
git tree: upstream
console+strace: https://syzkaller.appspot.com/x/log.txt?x=10850ea2580000
kernel config: https://syzkaller.appspot.com/x/.config?x=5f2996d42fef6c09
dashboard link: https://syzkaller.appspot.com/bug?extid=7f04e5b3fea8b6c33d39
compiler: gcc (Debian 12.2.0-14+deb12u1) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10ec9042580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14850ea2580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/5166c0e1d4f0/disk-6e64f458.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/0d6654192cf8/vmlinux-6e64f458.xz
kernel image: https://storage.googleapis.com/syzbot-assets/239aaa681481/bzImage-6e64f458.xz
The issue was bisected to:
commit 087f997870a948820ec366701d178f402c6a23a3
Author: Pavel Begunkov <asml.silence@gmail.com>
Date: Fri Nov 29 13:34:32 2024 +0000
io_uring/memmap: implement mmap for regions
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=157afea2580000
final oops: https://syzkaller.appspot.com/x/report.txt?x=177afea2580000
console output: https://syzkaller.appspot.com/x/log.txt?x=137afea2580000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+7f04e5b3fea8b6c33d39@syzkaller.appspotmail.com
Fixes: 087f997870a9 ("io_uring/memmap: implement mmap for regions")
------------[ cut here ]------------
WARNING: CPU: 1 PID: 5851 at mm/vmalloc.c:542 vmap_pages_pte_range mm/vmalloc.c:542 [inline]
WARNING: CPU: 1 PID: 5851 at mm/vmalloc.c:542 vmap_pages_pmd_range mm/vmalloc.c:569 [inline]
WARNING: CPU: 1 PID: 5851 at mm/vmalloc.c:542 vmap_pages_pud_range mm/vmalloc.c:587 [inline]
WARNING: CPU: 1 PID: 5851 at mm/vmalloc.c:542 vmap_pages_p4d_range mm/vmalloc.c:605 [inline]
WARNING: CPU: 1 PID: 5851 at mm/vmalloc.c:542 vmap_small_pages_range_noflush+0x984/0xc90 mm/vmalloc.c:627
Modules linked in:
CPU: 1 UID: 0 PID: 5851 Comm: syz-executor194 Not tainted 6.16.0-syzkaller-11952-g6e64f4580381 #0 PREEMPT(full)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025
RIP: 0010:vmap_pages_pte_range mm/vmalloc.c:542 [inline]
RIP: 0010:vmap_pages_pmd_range mm/vmalloc.c:569 [inline]
RIP: 0010:vmap_pages_pud_range mm/vmalloc.c:587 [inline]
RIP: 0010:vmap_pages_p4d_range mm/vmalloc.c:605 [inline]
RIP: 0010:vmap_small_pages_range_noflush+0x984/0xc90 mm/vmalloc.c:627
Code: 4d 89 f4 4d 21 ec 4c 89 e7 e8 98 6c ab ff 4d 39 ec 75 68 e8 de 71 ab ff 4c 09 eb e9 c8 fd ff ff 4c 8b 34 24 e8 cd 71 ab ff 90 <0f> 0b 90 e9 fc fe ff ff e8 bf 71 ab ff 4c 89 e7 e8 07 00 f7 ff 31
RSP: 0018:ffffc90002ea7990 EFLAGS: 00010293
RAX: 0000000000000000 RBX: ffffea0003000000 RCX: ffffffff82101e9f
RDX: ffff888025be2440 RSI: ffffffff82102153 RDI: 0000000000000005
RBP: ffff8880505c4508 R08: 0000000000000005 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
R13: 8000000000000163 R14: 1ffff920005d4f47 R15: ffffc900602a1000
FS: 000055557d51e380(0000) GS:ffff8881247c4000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055dad0a404b0 CR3: 0000000071b22000 CR4: 00000000003526f0
Call Trace:
<TASK>
__vmap_pages_range_noflush mm/vmalloc.c:656 [inline]
vmap_pages_range_noflush mm/vmalloc.c:681 [inline]
vmap_pages_range mm/vmalloc.c:701 [inline]
vmap+0x1aa/0x320 mm/vmalloc.c:3515
io_region_init_ptr io_uring/memmap.c:125 [inline]
io_create_region+0x605/0xd40 io_uring/memmap.c:228
io_create_region_mmap_safe+0xb2/0x170 io_uring/memmap.c:245
io_register_mem_region io_uring/register.c:616 [inline]
__io_uring_register+0x59f/0x2440 io_uring/register.c:836
__do_sys_io_uring_register io_uring/register.c:929 [inline]
__se_sys_io_uring_register io_uring/register.c:906 [inline]
__x64_sys_io_uring_register+0x169/0x280 io_uring/register.c:906
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xcd/0x4c0 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7ff9c19ee429
Code: 48 83 c4 28 c3 e8 37 17 00 00 0f 1f 80 00 00 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 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffec21487c8 EFLAGS: 00000246 ORIG_RAX: 00000000000001ab
RAX: ffffffffffffffda RBX: 0000000000000045 RCX: 00007ff9c19ee429
RDX: 0000200000000200 RSI: 0000000000000022 RDI: 0000000000000003
RBP: 0000000000000003 R08: 0000000000000000 R09: 00007ff9c1a66220
R10: 0000000000000001 R11: 0000000000000246 R12: 0000200000000300
R13: 0000200000000100 R14: 0000000000000001 R15: 0000000000000001
</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 syzkaller@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title
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.
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
next reply other threads:[~2025-08-11 17:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-11 17:54 syzbot [this message]
2025-08-11 19:36 ` [syzbot] [io-uring?] WARNING in vmap_small_pages_range_noflush Jens Axboe
2025-08-11 19:36 ` syzbot
2025-08-11 19:52 ` Jens Axboe
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=689a2e53.050a0220.51d73.00a1.GAE@google.com \
--to=syzbot+7f04e5b3fea8b6c33d39@syzkaller.appspotmail.com \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.