From: Michal Kubecek <mkubecek@suse.cz>
To: David Miller <davem@davemloft.net>
Cc: stable@vger.kernel.org, netdev@vger.kernel.org,
Jiri Slaby <jslaby@suse.cz>, Greg KH <gregkh@linuxfoundation.org>,
Sasha Levin <sasha.levin@oracle.com>
Subject: please queue commit ac37e2515c1a for stable 3.12 - 3.18
Date: Thu, 4 Jun 2015 22:54:03 +0200 [thread overview]
Message-ID: <20150604205403.GA24969@unicorn.suse.cz> (raw)
Hello,
please queue mainline commit
ac37e2515c1a ("xfrm: release dst_orig in case of error in xfrm_lookup()")
for stable branches 3.12, 3.14 and 3.18. It fixes a dst_entry reference
leak introduced by commit
f92ee61982d6 ("xfrm: Generate blackhole routes only from route lookup functions")
present in these branches (3.12 and 3.14 as a backport, 3.18 from
mainline). The patch applies cleanly to all three and I tested that it
fixes the issue in 3.12.
Michal Kubecek
next reply other threads:[~2015-06-04 20:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-04 20:54 Michal Kubecek [this message]
2015-06-26 12:59 ` please queue commit ac37e2515c1a for stable 3.12 - 3.18 Jiri Slaby
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=20150604205403.GA24969@unicorn.suse.cz \
--to=mkubecek@suse.cz \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=netdev@vger.kernel.org \
--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 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).