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 2018-01-11
Date: Fri, 12 Jan 2018 10:33:10 -0500 (EST)	[thread overview]
Message-ID: <20180112.103310.1086862766677884892.davem@davemloft.net> (raw)
In-Reply-To: <20180111113746.28186-1-steffen.klassert@secunet.com>

From: Steffen Klassert <steffen.klassert@secunet.com>
Date: Thu, 11 Jan 2018 12:37:35 +0100

> 1) Don't allow to change the encap type on state updates.
>    The encap type is set on state initialization and
>    should not change anymore. From Herbert Xu.
> 
> 2) Skip dead policies when rehashing to fix a
>    slab-out-of-bounds bug in xfrm_hash_rebuild.
>    From Florian Westphal.
> 
> 3) Two buffer overread fixes in pfkey.
>    From Eric Biggers.
> 
> 4) Fix rcu usage in xfrm_get_type_offload,
>    request_module can sleep, so can't be used
>    under rcu_read_lock. From Sabrina Dubroca.
> 
> 5) Fix an uninitialized lock in xfrm_trans_queue.
>    Use __skb_queue_tail instead of skb_queue_tail
>    in xfrm_trans_queue as we don't need the lock.
>    From Herbert Xu.
> 
> 6) Currently it is possible to create an xfrm state with an
>    unknown encap type in ESP IPv4. Fix this by returning an
>    error on unknown encap types. Also from Herbert Xu.
> 
> 7) Fix sleeping inside a spinlock in xfrm_policy_cache_flush.
>    From Florian Westphal.
> 
> 8) Fix ESP GRO when the headers not fully in the linear part
>    of the skb. We need to pull before we can access them.
> 
> 9) Fix a skb leak on error in key_notify_policy.
> 
> 10) Fix a race in the xdst pcpu cache, we need to
>     run the resolver routines with bottom halfes
>     off like the old flowcache did.
> 
> Please pull or let me know if there are problems.

Pulled, thanks Steffen.

      parent reply	other threads:[~2018-01-12 15:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-11 11:37 pull request (net): ipsec 2018-01-11 Steffen Klassert
2018-01-11 11:37 ` [PATCH 01/11] xfrm: Forbid state updates from changing encap type Steffen Klassert
2018-01-11 11:37 ` [PATCH 02/11] xfrm: skip policies marked as dead while rehashing Steffen Klassert
2018-01-11 11:37 ` [PATCH 03/11] af_key: fix buffer overread in verify_address_len() Steffen Klassert
2018-01-11 11:37 ` [PATCH 04/11] af_key: fix buffer overread in parse_exthdrs() Steffen Klassert
2018-01-11 11:37 ` [PATCH 05/11] xfrm: fix rcu usage in xfrm_get_type_offload Steffen Klassert
2018-01-11 11:37 ` [PATCH 06/11] xfrm: Use __skb_queue_tail in xfrm_trans_queue Steffen Klassert
2018-01-11 11:37 ` [PATCH 07/11] xfrm: Return error on unknown encap_type in init_state Steffen Klassert
2018-01-11 11:37 ` [PATCH 08/11] xfrm: don't call xfrm_policy_cache_flush while holding spinlock Steffen Klassert
2018-01-11 11:37 ` [PATCH 09/11] esp: Fix GRO when the headers not fully in the linear part of the skb Steffen Klassert
2018-01-11 11:37 ` [PATCH 10/11] af_key: Fix memory leak in key_notify_policy Steffen Klassert
2018-01-11 11:37 ` [PATCH 11/11] xfrm: Fix a race in the xdst pcpu cache Steffen Klassert
2018-01-12 15:33 ` 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=20180112.103310.1086862766677884892.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).