From: Luis Henriques <luis.henriques@canonical.com>
To: Ilya Dryomov <idryomov@gmail.com>
Cc: stable@vger.kernel.org
Subject: Re: Request for inclusion: commit 3ebe138ac642 for 3.10+
Date: Thu, 29 Oct 2015 13:05:45 +0000 [thread overview]
Message-ID: <20151029130545.GA2777@ares> (raw)
In-Reply-To: <CAOi1vP_wm49p6CxminB_xWbBD0besExiy38UrTAEZwr8FiTB-A@mail.gmail.com>
On Fri, Oct 23, 2015 at 06:38:49PM +0200, Ilya Dryomov wrote:
> Hello,
>
> Please queue 3ebe138ac642 ("rbd: fix double free on rbd_dev->header_name",
> went into 4.3-rc1) for 3.10+. It's going to be a prerequisite for the
> yet to be merged in mainline commits 1f2c6651f69c ("rbd: don't leak
> parent_spec in rbd_dev_probe_parent()") and 6d69bb536bac ("rbd: prevent
> kernel stack blow up on rbd map").
>
Thanks, I'm queuing it for the 3.16 kernel.
Cheers,
--
Lu�s
prev parent reply other threads:[~2015-10-29 13:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-23 16:38 Request for inclusion: commit 3ebe138ac642 for 3.10+ Ilya Dryomov
2015-10-29 13:05 ` Luis Henriques [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=20151029130545.GA2777@ares \
--to=luis.henriques@canonical.com \
--cc=idryomov@gmail.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 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).