Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Helge Deller <deller@gmx.de>,
	Christoph Biedl <linux-kernel.bfrz@manchmal.in-ulm.de>,
	linux-parisc@vger.kernel.org, io-uring@vger.kernel.org
Cc: Mike Rapoport <rppt@kernel.org>, Vlastimil Babka <vbabka@suse.cz>
Subject: Re: [PATCH] io_uring/parisc: Adjust pgoff in io_uring mmap() for parisc
Date: Mon, 7 Aug 2023 12:33:22 -0600	[thread overview]
Message-ID: <f5cc80b6-566d-816f-7fd9-099c58cca3d0@kernel.dk> (raw)
In-Reply-To: <ac18c4d4-7ca2-4648-77d2-3053c1de93f7@gmx.de>

On 8/7/23 12:27?PM, Helge Deller wrote:
> On 8/7/23 20:24, Jens Axboe wrote:
>> On 8/7/23 12:04?PM, Helge Deller wrote:
>>> The changes from commit 32832a407a71 ("io_uring: Fix io_uring mmap() by
>>> using architecture-provided get_unmapped_area()") to the parisc
>>> implementation of get_unmapped_area() broke glibc's locale-gen
>>> executable when running on parisc.
>>>
>>> This patch reverts those architecture-specific changes, and instead
>>> adjusts in io_uring_mmu_get_unmapped_area() the pgoff offset which is
>>> then given to parisc's get_unmapped_area() function.  This is much
>>> cleaner than the previous approach, and we still will get a coherent
>>> addresss.
>>>
>>> This patch has no effect on other architectures (SHM_COLOUR is only
>>> defined on parisc), and the liburing testcase stil passes on parisc.
>>
>> What branch is this against? It doesn't apply to my 6.5 io_uring branch,
>> which is odd as that's where the previous commits went through.
> 
> applies for me on git head / Linux 6.5-rc5

Hmm, maybe something unrelated then. I'll take a look. The patch is
garbled fwiw, but that's nothing new. If you download the raw one from
lore you can see how.

-- 
Jens Axboe


  reply	other threads:[~2023-08-07 18:33 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-01 19:37 Regression with kernel 6.4 "swapper: page allocation failure: order:0, mode:0x100(__GFP_ZERO) Christoph Biedl
2023-08-01 21:31 ` John David Anglin
2023-08-02  9:56 ` Mike Rapoport
2023-08-02 19:20   ` Christoph Biedl
2023-08-02 19:55     ` John David Anglin
2023-08-06 19:21     ` Christoph Biedl
2023-08-06 19:54       ` Helge Deller
2023-08-06 19:59         ` Helge Deller
2023-08-07 18:04           ` [PATCH] io_uring/parisc: Adjust pgoff in io_uring mmap() for parisc Helge Deller
2023-08-07 18:24             ` Jens Axboe
2023-08-07 18:27               ` Helge Deller
2023-08-07 18:33                 ` Jens Axboe [this message]
2023-08-07 19:30                   ` Helge Deller
2023-08-07 18:34             ` Jens Axboe
2023-08-07 19:33               ` Helge Deller
2023-08-07 19:55                 ` 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=f5cc80b6-566d-816f-7fd9-099c58cca3d0@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=deller@gmx.de \
    --cc=io-uring@vger.kernel.org \
    --cc=linux-kernel.bfrz@manchmal.in-ulm.de \
    --cc=linux-parisc@vger.kernel.org \
    --cc=rppt@kernel.org \
    --cc=vbabka@suse.cz \
    /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