stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Sasha Levin <sashal@kernel.org>
Cc: navid.emamdoost@gmail.com, dan.carpenter@gmail.com,
	stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] Staging: fbtft: fix memory leak in fbtft_framebuffer_alloc" failed to apply to 4.14-stable tree
Date: Tue, 15 Oct 2019 08:08:46 +0200	[thread overview]
Message-ID: <20191015060846.GA923323@kroah.com> (raw)
In-Reply-To: <20191015004305.GF31224@sasha-vm>

On Mon, Oct 14, 2019 at 08:43:05PM -0400, Sasha Levin wrote:
> On Mon, Oct 14, 2019 at 04:59:31PM +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
> > 
> > ------------------ original commit in Linus's tree ------------------
> > 
> > > From 5bdea6060618cfcf1459dca137e89aee038ac8b9 Mon Sep 17 00:00:00 2001
> > From: Navid Emamdoost <navid.emamdoost@gmail.com>
> > Date: Sun, 29 Sep 2019 22:09:45 -0500
> > Subject: [PATCH] Staging: fbtft: fix memory leak in fbtft_framebuffer_alloc
> > 
> > In fbtft_framebuffer_alloc the error handling path should take care of
> > releasing frame buffer after it is allocated via framebuffer_alloc, too.
> > Therefore, in two failure cases the goto destination is changed to
> > address this issue.
> > 
> > Fixes: c296d5f9957c ("staging: fbtft: core support")
> > Signed-off-by: Navid Emamdoost <navid.emamdoost@gmail.com>
> > Reviewed-by: Dan Carpenter <dan.carpenter@gmail.com>
> > Cc: stable <stable@vger.kernel.org>
> > Link: https://lore.kernel.org/r/20190930030949.28615-1-navid.emamdoost@gmail.com
> > Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> 
> Conflicts due to 333c7b940526b ("staging: fbtft: Fixes some alignment
> issues - Style"). Fixed up and queued for 4.14-4.4.

Thanks for fixing this one, and the other failures up.

greg k-h

      reply	other threads:[~2019-10-15  6:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-14 14:59 FAILED: patch "[PATCH] Staging: fbtft: fix memory leak in fbtft_framebuffer_alloc" failed to apply to 4.14-stable tree gregkh
2019-10-15  0:43 ` Sasha Levin
2019-10-15  6:08   ` Greg KH [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=20191015060846.GA923323@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=dan.carpenter@gmail.com \
    --cc=navid.emamdoost@gmail.com \
    --cc=sashal@kernel.org \
    --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 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).