netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steffen Klassert <steffen.klassert@secunet.com>
To: David Miller <davem@davemloft.net>
Cc: <herbert@gondor.apana.org.au>, <netdev@vger.kernel.org>
Subject: Re: pull request (net): ipsec 2017-10-24
Date: Tue, 24 Oct 2017 13:35:25 +0200	[thread overview]
Message-ID: <20171024113525.GL3323@secunet.com> (raw)
In-Reply-To: <20171024.201832.1079896012824825450.davem@davemloft.net>

On Tue, Oct 24, 2017 at 08:18:32PM +0900, David Miller wrote:
> From: Steffen Klassert <steffen.klassert@secunet.com>
> Date: Tue, 24 Oct 2017 12:37:38 +0200
> 
> > 1) Fix a memleak when we don't find a inner_mode
> >    during bundle creation. From David Miller.
> > 
> > 2) Fix a xfrm policy dump crash. We may crash
> >    on error when dumping policies via netlink.
> >    Fix this by initializing the policy walk
> >    with the cb->start method. This fix is a
> >    serious stable candidate. From Herbert Xu.
> > 
> > Please pull or let me know if there are problems.
> 
> Pulled, please submit #2 to -stable indeed!

I can do so, but whenever I sent something networking related
to -stable, it was ignored. I think this is because Greg expects
that you do the stable submissions for networking.

  reply	other threads:[~2017-10-24 11:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-24 10:37 pull request (net): ipsec 2017-10-24 Steffen Klassert
2017-10-24 10:37 ` [PATCH 1/2] ipsec: Fix dst leak in xfrm_bundle_create() Steffen Klassert
2017-10-24 10:37 ` [PATCH 2/2] ipsec: Fix aborted xfrm policy dump crash Steffen Klassert
2017-10-24 11:18 ` pull request (net): ipsec 2017-10-24 David Miller
2017-10-24 11:35   ` Steffen Klassert [this message]
2017-10-24 11:42     ` David Miller

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=20171024113525.GL3323@secunet.com \
    --to=steffen.klassert@secunet.com \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=netdev@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).