Message ID | 20230207133916.3109147-1-dhowells@redhat.com (mailing list archive) |
---|---|
Headers | show |
Series | iomap, splice: Fix DIO/splice_read race memory corruptor and kill off ITER_PIPE | expand |
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.
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