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>,
matoro <matoro_mailinglist_kernel@matoro.tk>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [PATCH 2/2] ia64: mmap: Consider pgoff when searching for free mapping
Date: Fri, 21 Jul 2023 17:24:32 +0200 [thread overview]
Message-ID: <20230721152432.196382-3-deller@gmx.de> (raw)
In-Reply-To: <20230721152432.196382-1-deller@gmx.de>
IA64 is the only architecture which does not consider the pgoff value when
searching for a possible free memory region with vm_unmapped_area().
Adding this seems to have no negative side effect on IA64, so add it now
to make IA64 consistent with all other architectures.
Signed-off-by: Helge Deller <deller@gmx.de>
Tested-by: matoro <matoro_mailinglist_kernel@matoro.tk>
Cc: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-ia64@vger.kernel.org
---
arch/ia64/kernel/sys_ia64.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/ia64/kernel/sys_ia64.c b/arch/ia64/kernel/sys_ia64.c
index 6e948d015332..eb561cc93632 100644
--- a/arch/ia64/kernel/sys_ia64.c
+++ b/arch/ia64/kernel/sys_ia64.c
@@ -63,7 +63,7 @@ arch_get_unmapped_area (struct file *filp, unsigned long addr, unsigned long len
info.low_limit = addr;
info.high_limit = TASK_SIZE;
info.align_mask = align_mask;
- info.align_offset = 0;
+ info.align_offset = pgoff << PAGE_SHIFT;
return vm_unmapped_area(&info);
}
--
2.41.0
next prev parent 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 [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 ` Helge Deller [this message]
2023-07-21 15:42 ` [PATCH 0/2] " 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-3-deller@gmx.de \
--to=deller@gmx.de \
--cc=akpm@linux-foundation.org \
--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 \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).