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-next): ipsec-next 2014-02-24
Date: Mon, 24 Feb 2014 18:17:55 -0500 (EST)	[thread overview]
Message-ID: <20140224.181755.1278751544217103372.davem@davemloft.net> (raw)
In-Reply-To: <1393236001-2445-1-git-send-email-steffen.klassert@secunet.com>

From: Steffen Klassert <steffen.klassert@secunet.com>
Date: Mon, 24 Feb 2014 10:59:48 +0100

> 1) Introduce skb_to_sgvec_nomark function to add further data to the sg list
>    without calling sg_unmark_end first. Needed to add extended sequence
>    number informations. From Fan Du.
> 
> 2) Add IPsec extended sequence numbers support to the Authentication Header
>    protocol for ipv4 and ipv6. From Fan Du.
> 
> 3) Make the IPsec flowcache namespace aware, from Fan Du.
> 
> 4) Avoid creating temporary SA for every packet when no key manager is
>    registered. From Horia Geanta.
> 
> 5) Support filtering of SA dumps to show only the SAs that match a
>    given filter. From Nicolas Dichtel.
> 
> 6) Remove caching of xfrm_policy_sk_bundles. The cached socket policy bundles
>    are never used, instead we create a new cache entry whenever xfrm_lookup()
>    is called on a socket policy. Most protocols cache the used routes to the
>    socket, so this caching is not needed.
> 
> 7)  Fix a forgotten SADB_X_EXT_FILTER length check in pfkey, from Nicolas
>     Dichtel.
> 
> 8) Cleanup error handling of xfrm_state_clone.
> 
> Please pull or let me know if there are problems.

Pulled, thanks a lot Steffen.

      parent reply	other threads:[~2014-02-24 23:17 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-24  9:59 pull request (net-next): ipsec-next 2014-02-24 Steffen Klassert
2014-02-24  9:59 ` [PATCH 01/13] skbuff: Introduce skb_to_sgvec_nomark to map skb without mark new end Steffen Klassert
2014-02-24  9:59 ` [PATCH 02/13] {IPv4,xfrm} Add ESN support for AH egress part Steffen Klassert
2014-02-24  9:59 ` [PATCH 03/13] {IPv4,xfrm} Add ESN support for AH ingress part Steffen Klassert
2014-02-24  9:59 ` [PATCH 04/13] {IPv6,xfrm} Add ESN support for AH egress part Steffen Klassert
2014-02-24  9:59 ` [PATCH 05/13] {IPv6,xfrm} Add ESN support for AH ingress part Steffen Klassert
2014-02-24  9:59 ` [PATCH 06/13] xfrm: Don't prohibit AH from using ESN feature Steffen Klassert
2014-02-24  9:59 ` [PATCH 07/13] flowcache: Make flow cache name space aware Steffen Klassert
2014-02-24  9:59 ` [PATCH 08/13] flowcache: Bring net/core/flow.c under IPsec maintain scope Steffen Klassert
2014-02-24  9:59 ` [PATCH 09/13] xfrm: avoid creating temporary SA when there are no listeners Steffen Klassert
2014-02-24  9:59 ` [PATCH 10/13] ipsec: add support of limited SA dump Steffen Klassert
2014-02-24  9:59 ` [PATCH 11/13] xfrm: Remove caching of xfrm_policy_sk_bundles Steffen Klassert
2014-02-24 10:00 ` [PATCH 12/13] pfkey: fix SADB_X_EXT_FILTER length check Steffen Klassert
2014-02-24 10:00 ` [PATCH 13/13] xfrm: Cleanup error handling of xfrm_state_clone Steffen Klassert
2014-02-24 23:17 ` 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=20140224.181755.1278751544217103372.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).