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 2019-07-05
Date: Fri, 05 Jul 2019 14:58:38 -0700 (PDT) [thread overview]
Message-ID: <20190705.145838.1520777700292544385.davem@davemloft.net> (raw)
In-Reply-To: <20190705082700.31107-1-steffen.klassert@secunet.com>
From: Steffen Klassert <steffen.klassert@secunet.com>
Date: Fri, 5 Jul 2019 10:26:53 +0200
> 1) Fix xfrm selector prefix length validation for
> inter address family tunneling.
> From Anirudh Gupta.
>
> 2) Fix a memleak in pfkey.
> From Jeremy Sowden.
>
> 3) Fix SA selector validation to allow empty selectors again.
> From Nicolas Dichtel.
>
> 4) Select crypto ciphers for xfrm_algo, this fixes some
> randconfig builds. From Arnd Bergmann.
>
> 5) Remove a duplicated assignment in xfrm_bydst_resize.
> From Cong Wang.
>
> 6) Fix a hlist corruption on hash rebuild.
> From Florian Westphal.
>
> 7) Fix a memory leak when creating xfrm interfaces.
> From Nicolas Dichtel.
>
> Please pull or let me know if there are problems.
Pulled, thanks Steffen.
prev parent reply other threads:[~2019-07-05 21:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-05 8:26 pull request (net): ipsec 2019-07-05 Steffen Klassert
2019-07-05 8:26 ` [PATCH 1/7] xfrm: Fix xfrm sel prefix length validation Steffen Klassert
2019-07-05 8:26 ` [PATCH 2/7] af_key: fix leaks in key_pol_get_resp and dump_sp Steffen Klassert
2019-07-05 8:26 ` [PATCH 3/7] xfrm: fix sa selector validation Steffen Klassert
2019-07-05 8:26 ` [PATCH 4/7] ipsec: select crypto ciphers for xfrm_algo Steffen Klassert
2019-07-05 8:26 ` [PATCH 5/7] xfrm: remove a duplicated assignment Steffen Klassert
2019-07-05 8:26 ` [PATCH 6/7] xfrm: policy: fix bydst hlist corruption on hash rebuild Steffen Klassert
2019-07-05 8:27 ` [PATCH 7/7] xfrm interface: fix memory leak on creation Steffen Klassert
2019-07-05 21:58 ` 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=20190705.145838.1520777700292544385.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).