From: Greg KH <gregkh@linuxfoundation.org>
To: Eduardo Valentin <eduval@amazon.com>
Cc: davem@davemloft.net, vallish@amazon.com, stable@vger.kernel.org,
stable-commits@vger.kernel.org
Subject: Re: Patch "bridge: mdb: fix leak on complete_info ptr on fail path" has been added to the 4.12-stable tree
Date: Tue, 18 Jul 2017 10:07:51 +0200 [thread overview]
Message-ID: <20170718080751.GA24935@kroah.com> (raw)
In-Reply-To: <20170718073554.GA16330@kroah.com>
On Tue, Jul 18, 2017 at 09:35:54AM +0200, Greg KH wrote:
> On Mon, Jul 17, 2017 at 11:32:07AM -0700, Eduardo Valentin wrote:
> > Greg,
> >
> >
> > On Mon, Jul 17, 2017 at 06:52:21PM +0200, gregkh@linuxfoundation.org wrote:
> > >
> > > This is a note to let you know that I've just added the patch titled
> > >
> > > bridge: mdb: fix leak on complete_info ptr on fail path
> > >
> > > to the 4.12-stable tree which can be found at:
> > > http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> > >
> > > The filename of the patch is:
> > > bridge-mdb-fix-leak-on-complete_info-ptr-on-fail-path.patch
> > > and it can be found in the queue-4.12 subdirectory.
> >
> > Can we get this patch also in the 4.9.y queue?
>
> Yes, please wait, I'm working on seeing what else needs to be backported
> to older stable kernels at the moment...
Now queued up, thanks.
greg k-h
prev parent reply other threads:[~2017-07-18 8:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-17 16:52 Patch "bridge: mdb: fix leak on complete_info ptr on fail path" has been added to the 4.12-stable tree gregkh
2017-07-17 18:32 ` Eduardo Valentin
2017-07-18 7:35 ` Greg KH
2017-07-18 8:07 ` 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=20170718080751.GA24935@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=davem@davemloft.net \
--cc=eduval@amazon.com \
--cc=stable-commits@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=vallish@amazon.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox