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-05-23
Date: Tue, 23 May 2017 10:54:21 -0400 (EDT) [thread overview]
Message-ID: <20170523.105421.498858429985702866.davem@davemloft.net> (raw)
In-Reply-To: <1495517624-27096-1-git-send-email-steffen.klassert@secunet.com>
From: Steffen Klassert <steffen.klassert@secunet.com>
Date: Tue, 23 May 2017 07:33:39 +0200
> 1) Fix wrong header offset for esp4 udpencap packets.
>
> 2) Fix a stack access out of bounds when creating a bundle
> with sub policies. From Sabrina Dubroca.
>
> 3) Fix slab-out-of-bounds in pfkey due to an incorrect
> sadb_x_sec_len calculation.
>
> 4) We checked the wrong feature flags when taking down
> an interface with IPsec offload enabled.
> Fix from Ilan Tayari.
>
> 5) Copy the anti replay sequence numbers when doing a state
> migration, otherwise we get out of sync with the sequence
> numbers. Fix from Antony Antony.
>
> Please pull or let me know if there are problems.
Pulled, thank you.
prev parent reply other threads:[~2017-05-23 14:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-23 5:33 pull request (net): ipsec 2017-05-23 Steffen Klassert
2017-05-23 5:33 ` [PATCH 1/5] esp4: Fix udpencap for local TCP packets Steffen Klassert
2017-05-23 5:33 ` [PATCH 2/5] xfrm: fix stack access out of bounds with CONFIG_XFRM_SUB_POLICY Steffen Klassert
2017-05-23 5:33 ` [PATCH 3/5] af_key: Fix slab-out-of-bounds in pfkey_compile_policy Steffen Klassert
2017-05-23 5:33 ` [PATCH 4/5] xfrm: Fix NETDEV_DOWN with IPSec offload Steffen Klassert
2017-05-23 5:33 ` [PATCH 5/5] xfrm: fix state migration copy replay sequence numbers Steffen Klassert
2017-05-23 14:54 ` 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=20170523.105421.498858429985702866.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).