[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZEAxhHx/4Ql6AMt2@casper.infradead.org>
Date: Wed, 19 Apr 2023 19:23:00 +0100
From: Matthew Wilcox <willy@...radead.org>
To: Lorenzo Stoakes <lstoakes@...il.com>
Cc: Jens Axboe <axboe@...nel.dk>, linux-mm@...ck.org,
linux-kernel@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>,
David Hildenbrand <david@...hat.com>,
Pavel Begunkov <asml.silence@...il.com>,
io-uring@...r.kernel.org, Jason Gunthorpe <jgg@...dia.com>
Subject: Re: [PATCH v4 4/6] io_uring: rsrc: avoid use of vmas parameter in
pin_user_pages()
On Wed, Apr 19, 2023 at 07:18:26PM +0100, Lorenzo Stoakes wrote:
> So even if I did the FOLL_ALLOW_BROKEN_FILE_MAPPING patch series first, I
> would still need to come along and delete a bunch of your code
> afterwards. And unfortunately Pavel's recent change which insists on not
> having different vm_file's across VMAs for the buffer would have to be
> reverted so I expect it might not be entirely without discussion.
I don't even understand why Pavel wanted to make this change. The
commit log really doesn't say.
commit edd478269640
Author: Pavel Begunkov <asml.silence@...il.com>
Date: Wed Feb 22 14:36:48 2023 +0000
io_uring/rsrc: disallow multi-source reg buffers
If two or more mappings go back to back to each other they can be passed
into io_uring to be registered as a single registered buffer. That would
even work if mappings came from different sources, e.g. it's possible to
mix in this way anon pages and pages from shmem or hugetlb. That is not
a problem but it'd rather be less prone if we forbid such mixing.
Cc: <stable@...r.kernel.org>
Signed-off-by: Pavel Begunkov <asml.silence@...il.com>
Signed-off-by: Jens Axboe <axboe@...nel.dk>
It even says "That is not a problem"! So why was this patch merged
if it's not fixing a problem?
It's now standing in the way of an actual cleanup. So why don't we
revert it? There must be more to it than this ...
Powered by blists - more mailing lists