On Thu, Apr 02, 2026 at 08:11:44AM -0700, Suren Baghdasaryan wrote: > On Thu, Apr 2, 2026 at 6:19 AM Lorenzo Stoakes (Oracle) <[email protected]> > wrote: > > > > On Tue, Mar 31, 2026 at 01:14:51PM -0700, Suren Baghdasaryan wrote: > > > On Tue, Mar 31, 2026 at 11:47 AM Lorenzo Stoakes (Oracle) > > > <[email protected]> wrote: > > > > > > > > On Tue, Mar 31, 2026 at 11:29:21AM -0700, Andrew Morton wrote: > > > > > On Tue, 31 Mar 2026 08:01:11 -0700 Suren Baghdasaryan > > > > > <[email protected]> wrote: > > > > > > > > > > > > Instead? That is, assuming we really need to care about this at > > > > > > > all. > > > > > > > > > > > > > > But I think I don't like this change at all? > > > > > > > > > > > > Yeah, this was the part I wasn't sure if it's worth adding. With > > > > > > your > > > > > > vote confirming my scepticism I'll go ahead and remove the parts I > > > > > > added to avoid extra vma_start_write_killable() call (3 instances in > > > > > > all) and will post v7. > > > > > > > > > > Thanks. I'll remove v6 from mm.git and shall await Lorenzo's advice > > > > > on > > > > > v7. > > > > > > > > > > > > > Ack, if we just drop the problematic bits we might still be fine for > > > > 7.1 :) > > > > > > Let's get your cleanup first and then see where we are. I also hate > > > the way I have to report a fake error code, so with that cleanup the > > > patchset should be much nicer. > > > > Ack, yeah it's horrid, + _my fault_ :) > > No worries, I can wait. > > > > > I can put something together now perhaps that can potentially be queued up > > for > > 7.2 at 7.1-rc1. > > Thanks! That would be appreciated.
This might not quite be 'now' as of course it's grown into something much bigger :P Cheers, Lorenzo
