From: Jens Axboe <[email protected]>
To: [email protected], [email protected],
[email protected], Jiri Slaby <[email protected]>,
[email protected], Helge Deller <[email protected]>
Subject: Re: [PATCH 0/2] io_uring: Fix io_uring mmap() by using architecture-provided get_unmapped_area()
Date: Fri, 21 Jul 2023 09:42:04 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On Fri, 21 Jul 2023 17:24:30 +0200, Helge Deller wrote:
> Fix io_uring on IA64 (and x86-32?) which was broken since commit
> d808459b2e31 ("io_uring: Adjust mapping wrt architecture aliasing
> requirements").
> The fix is to switch back to the get_unmapped_area() which is provided by
> each architecture.
>
> Patch 1 switches io_uring back to use per-arch get_unmapped_area().
> Patch 2 (for IA64) is an independend cleanup.
>
> [...]
Applied, thanks!
[1/2] io_uring: Fix io_uring mmap() by using architecture-provided get_unmapped_area()
commit: 32832a407a7178eec3215fad9b1a3298c14b0d69
[2/2] ia64: mmap: Consider pgoff when searching for free mapping
commit: 07e981137f17e5275b6fa5fd0c28b0ddb4519702
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2023-07-21 15:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-21 15:24 [PATCH 0/2] io_uring: Fix io_uring mmap() by using architecture-provided get_unmapped_area() Helge Deller
2023-07-21 15:24 ` [PATCH 1/2] " Helge Deller
2023-07-24 7:39 ` Jiri Slaby
2023-07-21 15:24 ` [PATCH 2/2] ia64: mmap: Consider pgoff when searching for free mapping Helge Deller
2023-07-21 15:42 ` [PATCH 0/2] io_uring: Fix io_uring mmap() by using architecture-provided get_unmapped_area() Jens Axboe
2023-07-21 15:42 ` 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=168995412429.284551.12005520905700806146.b4-ty@kernel.dk \
[email protected] \
[email protected] \
[email protected] \
[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