From: Jens Axboe <[email protected]>
To: [email protected], Pavel Begunkov <[email protected]>
Cc: [email protected]
Subject: Re: [PATCH 1/1] io_uring: check for overflows in io_pin_pages
Date: Tue, 26 Nov 2024 08:00:12 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <1b7520ddb168e1d537d64be47414a0629d0d8f8f.1732581026.git.asml.silence@gmail.com>
On Tue, 26 Nov 2024 00:34:18 +0000, Pavel Begunkov wrote:
> WARNING: CPU: 0 PID: 5834 at io_uring/memmap.c:144 io_pin_pages+0x149/0x180 io_uring/memmap.c:144
> CPU: 0 UID: 0 PID: 5834 Comm: syz-executor825 Not tainted 6.12.0-next-20241118-syzkaller #0
> Call Trace:
> <TASK>
> __io_uaddr_map+0xfb/0x2d0 io_uring/memmap.c:183
> io_rings_map io_uring/io_uring.c:2611 [inline]
> io_allocate_scq_urings+0x1c0/0x650 io_uring/io_uring.c:3470
> io_uring_create+0x5b5/0xc00 io_uring/io_uring.c:3692
> io_uring_setup io_uring/io_uring.c:3781 [inline]
> ...
> </TASK>
>
> [...]
Applied, thanks!
[1/1] io_uring: check for overflows in io_pin_pages
commit: 0c0a4eae26ac78379d0c1db053de168a8febc6c9
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2024-11-26 15:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-26 0:34 [PATCH 1/1] io_uring: check for overflows in io_pin_pages Pavel Begunkov
2024-11-26 15:00 ` 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=173263321276.43959.14162906343487265344.b4-ty@kernel.dk \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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