Re: [GIT PULL] Additional MM updates for 6.16-rc1

[Matthew Wilcox <willy@infradead.org>]

On Mon, Jun 02, 2025 at 12:17:51PM -0700, Andrew Morton wrote:
> On Mon, 2 Jun 2025 16:05:38 +0100 Matthew Wilcox <willy@infradead.org> wrote:
> 
> > On Sun, Jun 01, 2025 at 03:12:22PM -0700, Andrew Morton wrote:
> > > Linus, please merge this second batch of MM updates for the 6.16-rcX cycle.
> > 
> > A word of warning for Linus since he wouldn't've been cc'd on the
> > earlier email.  This branch is based on v6.15-rc6 but contains a
> > commit which depends on 97dfbbd135cb which was merged during the
> > current merge window.  You might want to do a rebase or ask Andrew to
> > do it in order to prevent a bisection hazard.
> > 
> > 0day-ci found the problem here:
> > https://lore.kernel.org/linux-mm/202506022027.IYQzZghL-lkp@intel.com/
> 
> I think it's OK?  I did the merge and 
> 
> 	d9736929445e iov: remove copy_page_from_iter_atomic()
> 
> lands later than
> 
> 	97dfbbd135cb highmem: add folio_test_partial_kmap()

Yes, but if 'git bisect' lands you on there being a problem in 0b43b8bc8ef8
you won't be able to build it because 0b43b8bc8ef8 has d9736929445e as
an ancestor but not 97dfbbd135cb .  You'll need to add a cherry-pick of
97dfbbd135cb which is aggravating and we try to avoid this.