From: Helge Deller <deller@gmx.de>
To: linux-kernel@vger.kernel.org, io-uring@vger.kernel.org,
Jens Axboe <axboe@kernel.dk>,
linux-ia64@vger.kernel.org, Jiri Slaby <jirislaby@kernel.org>,
linux-parisc@vger.kernel.org
Cc: Helge Deller <deller@gmx.de>
Subject: [PATCH 0/2] io_uring: Fix io_uring mmap() by using architecture-provided get_unmapped_area()
Date: Fri, 21 Jul 2023 17:24:30 +0200 [thread overview]
Message-ID: <20230721152432.196382-1-deller@gmx.de> (raw)
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.
Helge
Helge Deller (2):
io_uring: Fix io_uring mmap() by using architecture-provided
get_unmapped_area()
ia64: mmap: Consider pgoff when searching for free mapping
arch/ia64/kernel/sys_ia64.c | 2 +-
arch/parisc/kernel/sys_parisc.c | 15 ++++++++----
io_uring/io_uring.c | 42 +++++++++++++--------------------
3 files changed, 28 insertions(+), 31 deletions(-)
--
2.41.0
next reply other threads:[~2023-07-21 15:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-21 15:24 Helge Deller [this message]
2023-07-21 15:24 ` [PATCH 1/2] io_uring: Fix io_uring mmap() by using architecture-provided get_unmapped_area() 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
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=20230721152432.196382-1-deller@gmx.de \
--to=deller@gmx.de \
--cc=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=jirislaby@kernel.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
/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