netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: steffen.klassert@secunet.com
Cc: herbert@gondor.apana.org.au, netdev@vger.kernel.org
Subject: Re: pull request (net): ipsec 2017-04-19
Date: Thu, 20 Apr 2017 16:20:17 -0400 (EDT)	[thread overview]
Message-ID: <20170420.162017.1677591279608729707.davem@davemloft.net> (raw)
In-Reply-To: <1492578636-621-1-git-send-email-steffen.klassert@secunet.com>

From: Steffen Klassert <steffen.klassert@secunet.com>
Date: Wed, 19 Apr 2017 07:10:34 +0200

> Two fixes for af_key:
> 
> 1) Add a lock to key dump to prevent a NULL pointer dereference.
>    From Yuejie Shi.
> 
> 2) Fix slab-out-of-bounds in parse_ipsecrequests.
>    From Herbert Xu.
> 
> Please pull or let me know if there are problems.

Pulled, thanks Steffen.

      parent reply	other threads:[~2017-04-20 20:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-19  5:10 pull request (net): ipsec 2017-04-19 Steffen Klassert
2017-04-19  5:10 ` [PATCH 1/2] af_key: Add lock to key dump Steffen Klassert
2017-04-19  5:10 ` [PATCH 2/2] af_key: Fix sadb_x_ipsecrequest parsing Steffen Klassert
2017-04-20 20:20 ` David Miller [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=20170420.162017.1677591279608729707.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=netdev@vger.kernel.org \
    --cc=steffen.klassert@secunet.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;
as well as URLs for NNTP newsgroup(s).