All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Sebastian Gottschall <s.gottschall@dd-wrt.com>
Cc: Huacai Chen <chenhc@lemote.com>,
	Lukasz Odzioba <lukasz.odzioba@intel.com>,
	Sasha Levin <sasha.levin@oracle.com>,
	stable@vger.kernel.org
Subject: Re: [PATCH][stable-4.1/3.18] mm/swap.c: Fix a copy&paste error during backport
Date: Sun, 24 Jul 2016 13:41:34 -0700	[thread overview]
Message-ID: <20160724204134.GA7801@kroah.com> (raw)
In-Reply-To: <e0ef0e35-9f0e-8d14-cfda-f960d3b404a2@dd-wrt.com>

On Sun, Jul 24, 2016 at 03:30:38PM +0200, Sebastian Gottschall wrote:
> Am 23.07.2016 um 18:42 schrieb Greg Kroah-Hartman:
> > On Sat, Jul 23, 2016 at 05:30:47PM +0800, Huacai Chen wrote:
> > > When backport 8f182270dfec432e ("mm/swap.c: flush lru pvecs on compound
> > > page arrival") to 4.1/3.18 stable branches, there is a copy&paste error
> > > which will cause memory leak and then an OOM.
> > > 
> > > Signed-off-by: Huacai Chen <chenhc@lemote.com>
> > > ---
> > >   mm/swap.c | 2 +-
> > >   1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > I am not the maintainer of these kernels, it is Sasha, so there's not
> > much I can do here, sorry.
>
> consider that sasha is not on this list anymore. his email address is
> invalid. i dont think that he got notice of it and its a bad situation if
> stable kernels are broken. (since more than a week)

I trust he will return, give him a chance :)

In the meantime, just apply the patch as needed to your local copies of
the tree, or upgrade to a newer release.

thanks,

greg k-h

      reply	other threads:[~2016-07-24 20:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-23  9:30 [PATCH][stable-4.1/3.18] mm/swap.c: Fix a copy&paste error during backport Huacai Chen
2016-07-23 16:42 ` Greg Kroah-Hartman
2016-07-24 13:30   ` Sebastian Gottschall
2016-07-24 20:41     ` Greg Kroah-Hartman [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=20160724204134.GA7801@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=chenhc@lemote.com \
    --cc=lukasz.odzioba@intel.com \
    --cc=s.gottschall@dd-wrt.com \
    --cc=sasha.levin@oracle.com \
    --cc=stable@vger.kernel.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 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.