[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d9247209-bca2-4650-b1c7-72e77990411d@kernel.dk>
Date: Tue, 7 Feb 2023 07:30:07 -0700
From: Jens Axboe <axboe@...nel.dk>
To: David Howells <dhowells@...hat.com>,
Al Viro <viro@...iv.linux.org.uk>,
Christoph Hellwig <hch@...radead.org>
Cc: 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
On 2/7/23 6:39?AM, David Howells wrote:
> [!] 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?
I'll check in on these two patches later today, but just wanted to say
that we can definitely just toss the existing branch, and setup a new
one based on -rc7 that adds these two first, then pulls in the other
branch on top to avoid this. Not a big deal, and warranted in this case.
--
Jens Axboe
Powered by blists - more mailing lists