Re: FAILED: patch "[PATCH] mm: use vma_init() to initialize VMAs on stack and data" failed to apply to 4.17-stable tree

On Sun, Jul 29, 2018 at 06:39:51AM +0000, Greg Kroah-Hartman wrote:

On Sat, Jul 28, 2018 at 10:10:46AM -0700, Linus Torvalds wrote:

quoted

On Sat, Jul 28, 2018 at 1:00 AM [off-list ref] wrote:

quoted

The patch below does not apply to the 4.17-stable tree.

I suspect these three patches from Kirill just need these three
preparatory cleanup patches applied first:

  490fc053865c mm: make vm_area_alloc() initialize core fields
  95faf6992df4 mm: make vm_area_dup() actually copy the old vma data
  3928d4f5ee37 mm: use helper functions for allocating and freeing
vm_area structs

they weren't marked for stable, because they didn't actually change
any semantics (and I thought Kirill's patches would be delayed to the
next merge window).

Ok, so are these even needed now?

Yes, I think so.

But please postpone it for now. There's regression report on android.

Kirill, if they are, how far back should they go to?

Looks like the problem was there forever. Even before vma_is_anonymous()
was introduced.

-- 
 Kirill A. Shutemov