From: Steffen Klassert <steffen.klassert@secunet•com>
To: Fan Du <fan.du@windriver•com>
Cc: davem@davemloft•net, netdev@vger•kernel.org
Subject: Re: [PATCHv3 net-next 0/3] IPComp fixes
Date: Tue, 17 Dec 2013 12:37:58 +0100 [thread overview]
Message-ID: <20131217113758.GK31491@secunet.com> (raw)
In-Reply-To: <1387190870-32506-1-git-send-email-fan.du@windriver.com>
On Mon, Dec 16, 2013 at 06:47:47PM +0800, Fan Du wrote:
> Hi,
>
> This patchset includes bug fix focusing on IPComp mainly, which addresses
> IPComp Compression Parameter Index(CPI, 16bits of 32bits SPI value) problem.
>
> And other issue is the compression part, undesirable packet will not be
> compressed, and then send into wire, this packet will be dropped by policy
> checking in the receiver side.
>
> v2:
> Patch1: Clean up align issue from v1.
> Patch2: Introduce verify_userspi_info for pkfey and netlink interface
> to share code.
> Patch3: Add Documentation/networking/ipsec.txt to document known issues.
>
> v3:
> Patch2: Fix while space error.
> Patch3: Del empty line
>
> Fan Du (3):
> xfrm: check user specified spi for IPComp
> xfrm: export verify_userspi_info for pkfey and netlink interface
> xfrm: Add file to document IPsec corner case
>
All applied to ipsec-next, thanks Fan!
prev parent reply other threads:[~2013-12-17 11:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-16 10:47 [PATCHv3 net-next 0/3] IPComp fixes Fan Du
2013-12-16 10:47 ` [PATCHv3 net-next 1/3] xfrm: check user specified spi for IPComp Fan Du
2013-12-16 10:47 ` [PATCHv3 net-next 2/3] xfrm: export verify_userspi_info for pkfey and netlink interface Fan Du
2013-12-16 10:47 ` [PATCHv3 net-next 3/3] xfrm: Add file to document IPsec corner case Fan Du
2013-12-17 11:37 ` Steffen Klassert [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=20131217113758.GK31491@secunet.com \
--to=steffen.klassert@secunet$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=fan.du@windriver$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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