From: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andrea Arcangeli <aarcange@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Dmitry Vyukov <dvyukov@google.com>,
Oleg Nesterov <oleg@redhat.com>, stable <stable@vger.kernel.org>
Subject: Re: FAILED: patch "[PATCH] mm: use vma_init() to initialize VMAs on stack and data" failed to apply to 4.17-stable tree
Date: Mon, 30 Jul 2018 16:11:35 +0300 [thread overview]
Message-ID: <20180730131134.xipliyqusvyole5v@black.fi.intel.com> (raw)
In-Reply-To: <20180729063951.GA23815@kroah.com>
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:
> > On Sat, Jul 28, 2018 at 1:00 AM <gregkh@linuxfoundation.org> wrote:
> > >
> > > 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
prev parent reply other threads:[~2018-07-30 14:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-28 7:59 FAILED: patch "[PATCH] mm: use vma_init() to initialize VMAs on stack and data" failed to apply to 4.17-stable tree gregkh
2018-07-28 17:10 ` Linus Torvalds
2018-07-29 6:39 ` Greg Kroah-Hartman
2018-07-30 13:11 ` Kirill A. Shutemov [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180730131134.xipliyqusvyole5v@black.fi.intel.com \
--to=kirill.shutemov@linux.intel.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=dvyukov@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=oleg@redhat.com \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).