From: Jens Axboe <axboe@kernel.dk>
To: syzbot <syzbot+7f04e5b3fea8b6c33d39@syzkaller.appspotmail.com>
Cc: asml.silence@gmail.com, io-uring@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [io-uring?] WARNING in vmap_small_pages_range_noflush
Date: Mon, 11 Aug 2025 13:52:46 -0600 [thread overview]
Message-ID: <62f9321b-9ab5-4982-85f5-bc386d863a2b@kernel.dk> (raw)
In-Reply-To: <689a4635.050a0220.7f033.0101.GAE@google.com>
On 8/11/25 1:36 PM, syzbot wrote:
>> #syz dup "[syzbot] [io-uring?] WARNING in __vmap_pages_range_noflush"
>
> can't find the dup bug
Huh, did I mess that up? It's literally right here:
https://lore.kernel.org/io-uring/6895f766.050a0220.7f033.0064.GAE@google.com/T/#t
with that very subject line.
#syz dup [syzbot] [io-uring?] WARNING in __vmap_pages_range_noflush
--
Jens Axboe
prev parent reply other threads:[~2025-08-11 19:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-11 17:54 [syzbot] [io-uring?] WARNING in vmap_small_pages_range_noflush syzbot
2025-08-11 19:36 ` Jens Axboe
2025-08-11 19:36 ` syzbot
2025-08-11 19:52 ` Jens Axboe [this message]
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=62f9321b-9ab5-4982-85f5-bc386d863a2b@kernel.dk \
--to=axboe@kernel.dk \
--cc=asml.silence@gmail.com \
--cc=io-uring@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+7f04e5b3fea8b6c33d39@syzkaller.appspotmail.com \
--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