From: Jens Axboe <axboe@kernel.dk>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: io-uring@vger.kernel.org
Subject: Re: [PATCH] io_uring: take page references for NOMMU pbuf_ring mmaps
Date: Tue, 21 Apr 2026 08:02:51 -0600 [thread overview]
Message-ID: <023f90bc-9058-461d-bd68-956665ceed6d@kernel.dk> (raw)
In-Reply-To: <2026042108-fiscally-unglazed-56c7@gregkh>
On 4/21/26 7:55 AM, Greg Kroah-Hartman wrote:
> On Tue, Apr 21, 2026 at 07:50:32AM -0600, Jens Axboe wrote:
>> On 4/21/26 7:46 AM, Greg Kroah-Hartman wrote:
>>> Note, I have no way of testing this, I'm only forwarding this on because
>>> I got the bug report and was able to generate something that "seems"
>>
>> AI bug report I presume? Because I can't imagine anyone ever attempted
>> to run this.
>
> Yes, I got a bunch of "non-mmu" bug reports, which is a bit odd but I
> guess you can do that with qemu these days? I should dig into that,
> maybe that way I can test this and get a reproducer for you. If not,
> let's just bin the thing.
Was just pondering if I can run it in qemu. I'll take a look. But I knew
it'd be some kind of AI bs, because why else would anyone look at nommu
in the first place. But we have it in the codebase, so...
>>> correct, but it might be a total load of crap here, my knowledge of the
>>> vm layer is very low so take this for where it is coming from (i.e. a
>>> non-deterministic pattern matching system.)
>>>
>>> I do have another patch that just disables io_uring for !MMU systems, if
>>> you want that instead? Or is this feature something that !MMU devices
>>> actually care about?
>>
>> I mean, who really cares about !MMU in the first place, we should just
>> kill that off with a passion.
>>
>> Let me take a closer look at this and bounce it past some vm people, my
>> nommu knowledge is close to zero as it's never been relevant in my
>> professional life time. Which is saying something...
>
> Let me try to get a reproducer going first, let's not waste any more
> human time on this just yet, sorry for sending this out without that
> done first...
Thanks!
--
Jens Axboe
next prev parent reply other threads:[~2026-04-21 14:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-21 13:46 [PATCH] io_uring: take page references for NOMMU pbuf_ring mmaps Greg Kroah-Hartman
2026-04-21 13:50 ` Jens Axboe
2026-04-21 13:55 ` Greg Kroah-Hartman
2026-04-21 14:02 ` Jens Axboe [this message]
2026-04-21 16:01 ` Greg Kroah-Hartman
2026-04-21 16:05 ` Jens Axboe
2026-04-21 16:21 ` Jens Axboe
2026-04-21 16:24 ` Greg Kroah-Hartman
2026-04-21 16:41 ` Jens Axboe
2026-04-21 17:04 ` Jens Axboe
2026-04-21 17:38 ` Jens Axboe
2026-04-21 17:39 ` 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=023f90bc-9058-461d-bd68-956665ceed6d@kernel.dk \
--to=axboe@kernel.dk \
--cc=gregkh@linuxfoundation.org \
--cc=io-uring@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