From: Miles Chen <miles.chen@mediatek.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: <akpm@linux-foundation.org>, <cai@lca.pw>, <hannes@cmpxchg.org>,
<mhocko@suse.com>, <stable@vger.kernel.org>,
<torvalds@linux-foundation.org>, <vdavydov.dev@gmail.com>
Subject: Re: FAILED: patch "[PATCH] mm/memcontrol.c: fix use after free in mem_cgroup_iter()" failed to apply to 4.14-stable tree
Date: Sat, 17 Aug 2019 23:38:18 +0800 [thread overview]
Message-ID: <1566056298.6541.2.camel@mtkswgap22> (raw)
In-Reply-To: <20190817152744.GA16493@kroah.com>
On Sat, 2019-08-17 at 17:27 +0200, Greg KH wrote:
> On Sat, Aug 17, 2019 at 11:13:38PM +0800, Miles Chen wrote:
> > On Fri, 2019-08-16 at 17:37 +0200, Greg KH wrote:
> > > On Fri, Aug 16, 2019 at 07:07:20PM +0800, Miles Chen wrote:
> > > > On Fri, 2019-08-16 at 12:04 +0200, gregkh@linuxfoundation.org wrote:
> > > > > The patch below does not apply to the 4.14-stable tree.
> > > > > If someone wants it applied there, or to any other stable or longterm
> > > > > tree, then please email the backport, including the original git commit
> > > > > id to <stable@vger.kernel.org>.
> > > > >
> > > > > thanks,
> > > > >
> > > > > greg k-h
> > > > >
> > > > Hi Greg,
> > > >
> > > > Below this the backport for 4.14
> > >
> > > This backport, and the other 2, are all line-wrapped and the patch is
> > > corrupted and can not be applied :(
> >
> > Sorry for that.
> > >
> > > Can you fix up and resend? I can take an attachment if that is what is
> > > needed here.
> >
> > No problem. The backport patches are attached in this email.
>
> This didn't apply either. So I tried doing it "by hand" and it looks
> like you are not making these against the latest 4.14.y release (and
> other releases.) The difference is in a commit that showed up in
> 4.14.58, which was released July 2018.
>
> I'll take these as I've already fixed them up, but in the future, please
> make them against the latest version of the stable trees, not the
> "original" release that happened many years ago.
>
Sorry for that. I'll make the patches against the latest version of
stable tree next time.
thanks for you help.
cheers,
Miles
> thanks,
>
> greg k-h
prev parent reply other threads:[~2019-08-17 15:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-16 10:04 FAILED: patch "[PATCH] mm/memcontrol.c: fix use after free in mem_cgroup_iter()" failed to apply to 4.14-stable tree gregkh
2019-08-16 11:07 ` Miles Chen
2019-08-16 15:37 ` Greg KH
2019-08-17 15:13 ` Miles Chen
2019-08-17 15:27 ` Greg KH
2019-08-17 15:38 ` Miles Chen [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=1566056298.6541.2.camel@mtkswgap22 \
--to=miles.chen@mediatek.com \
--cc=akpm@linux-foundation.org \
--cc=cai@lca.pw \
--cc=gregkh@linuxfoundation.org \
--cc=hannes@cmpxchg.org \
--cc=mhocko@suse.com \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=vdavydov.dev@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.