From: Jiri Slaby <jirislaby@kernel.org>
To: Helge Deller <deller@gmx.de>,
linux-kernel@vger.kernel.org, io-uring@vger.kernel.org,
Jens Axboe <axboe@kernel.dk>,
linux-ia64@vger.kernel.org, linux-parisc@vger.kernel.org
Cc: matoro <matoro_mailinglist_kernel@matoro.tk>
Subject: Re: [PATCH 1/2] io_uring: Fix io_uring mmap() by using architecture-provided get_unmapped_area()
Date: Mon, 24 Jul 2023 09:39:07 +0200 [thread overview]
Message-ID: <047346f8-9ac4-4990-2885-8bfac47b83a3@kernel.org> (raw)
In-Reply-To: <20230721152432.196382-2-deller@gmx.de>
On 21. 07. 23, 17:24, Helge Deller wrote:
> The io_uring testcase is broken on IA-64 since commit d808459b2e31
> ("io_uring: Adjust mapping wrt architecture aliasing requirements").
>
> The reason is, that this commit introduced an own architecture
> independend get_unmapped_area() search algorithm which finds on IA-64 a
> memory region which is outside of the regular memory region used for
> shared userspace mappings and which can't be used on that platform
> due to aliasing.
>
> To avoid similar problems on IA-64 and other platforms in the future,
> it's better to switch back to the architecture-provided
> get_unmapped_area() function and adjust the needed input parameters
> before the call. Beside fixing the issue, the function now becomes
> easier to understand and maintain.
>
> This patch has been successfully tested with the io_uring testcase on
> physical x86-64, ppc64le, IA-64 and PA-RISC machines. On PA-RISC the LTP
> mmmap testcases did not report any regressions.
>
> Signed-off-by: Helge Deller <deller@gmx.de>
> Cc: Jens Axboe <axboe@kernel.dk>
> Reported-by: matoro <matoro_mailinglist_kernel@matoro.tk>
> Fixes: d808459b2e31 ("io_uring: Adjust mapping wrt architecture aliasing requirements")
Tested-by: Jiri Slaby <jirislaby@kernel.org>
thanks,
--
js
suse labs
next prev parent reply other threads:[~2023-07-24 7:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-21 15:24 [PATCH 0/2] " Helge Deller
2023-07-21 15:24 ` [PATCH 1/2] " Helge Deller
2023-07-24 7:39 ` Jiri Slaby [this message]
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=047346f8-9ac4-4990-2885-8bfac47b83a3@kernel.org \
--to=jirislaby@kernel.org \
--cc=axboe@kernel.dk \
--cc=deller@gmx.de \
--cc=io-uring@vger.kernel.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=matoro_mailinglist_kernel@matoro.tk \
/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
all inboxes | Powered by JetHome®