netdev - Re: pull request (net-next): ipsec-next 2017-02-01

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20170201.113847.394056137617535611.davem@davemloft.net>
Date:   Wed, 01 Feb 2017 11:38:47 -0500 (EST)
From:   David Miller <davem@...emloft.net>
To:     steffen.klassert@...unet.com
Cc:     herbert@...dor.apana.org.au, netdev@...r.kernel.org
Subject: Re: pull request (net-next): ipsec-next 2017-02-01

From: Steffen Klassert <steffen.klassert@...unet.com>
Date: Wed, 1 Feb 2017 09:17:42 +0100

> 1) Some typo fixes, from Alexander Alemayhu.
> 
> 2) Don't acquire state lock in get_mtu functions.
>    The only rece against a dead state does not matter.
>    From Florian Westphal.
> 
> 3) Remove xfrm4_state_fini, it is unused for more than
>    10 years. From Florian Westphal.
> 
> 4) Various rcu usage improvements. From Florian Westphal.
> 
> 5) Properly handle crypto arrors in ah4/ah6.
>    From Gilad Ben-Yossef.
> 
> 6) Try to avoid skb linearization in esp4 and esp6.
> 
> 7) The esp trailer is now set up in different places,
>    add a helper for this.
> 
> 8) With the upcomming usage of gro_cells in IPsec,
>    a gro merged skb can have a secpath. Drop it
>    before freeing or reusing the skb.
> 
> 9) Add a xfrm dummy network device for napi. With
>    this we can use gro_cells from within xfrm,
>    it allows IPsec GRO without impact on the generic
>    networking code.
> 
> Please pull or let me know if there are problems.

Looks great, pulled, thanks a lot!