[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <3417265.1675783322@warthog.procyon.org.uk>
Date: Tue, 07 Feb 2023 15:22:02 +0000
From: David Howells <dhowells@...hat.com>
To: Jens Axboe <axboe@...nel.dk>
Cc: dhowells@...hat.com, Al Viro <viro@...iv.linux.org.uk>,
Christoph Hellwig <hch@...radead.org>,
Matthew Wilcox <willy@...radead.org>, Jan Kara <jack@...e.cz>,
Jeff Layton <jlayton@...nel.org>,
David Hildenbrand <david@...hat.com>,
Jason Gunthorpe <jgg@...dia.com>,
Logan Gunthorpe <logang@...tatee.com>,
Hillf Danton <hdanton@...a.com>, linux-fsdevel@...r.kernel.org,
linux-block@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-mm@...ck.org
Subject: Re: [PATCH 0/2] iomap, splice: Fix DIO/splice_read race memory corruptor and kill off ITER_PIPE
Hi Jens,
> [!] Jens: Note that there's a window in the linux-block/for-next branch
> with a memory corruptor bug that someone bisecting might hit. These
> two patches would be better pushed to the front of my iov-extract
> branch to eliminate the window. Would it be possible for you to
> replace my branch in your for-next branch at this point?
In case you would prefer to do this, I've updated my iov-extract[*] branch to
put these two patches at the bottom and pushed the other patches back on top
of it, dropping the pipe extraction bits from the iov_iter_extract_pages()
patch in case you want to use that.
I've also removed the FOLL_PIN that was in that patch as it's implied by
calling pin_user_pages_fast() and is being made private to mm/.
I can also repost the full set of patches if that would be useful.
David
[*] https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git/log/?h=iov-extract
Powered by blists - more mailing lists