netdev - Re: [PATCH net-next v3 0/3] tipc: message reassembly using fragment chain

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: <20131107.183102.1693364426762289735.davem@davemloft.net>
Date:	Thu, 07 Nov 2013 18:31:02 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	erik.hugne@...csson.com
Cc:	netdev@...r.kernel.org, jon.maloy@...csson.com, maloy@...jonn.com,
	paul.gortmaker@...driver.com, ying.xue@...driver.com,
	tipc-discussion@...ts.sourceforge.net
Subject: Re: [PATCH net-next v3 0/3] tipc: message reassembly using
 fragment chain

From: <erik.hugne@...csson.com>
Date: Wed, 6 Nov 2013 09:28:04 +0100

> From: Erik Hugne <erik.hugne@...csson.com>
> 
> We introduce a new reassembly algorithm that improves performance
> and eliminates the risk of causing out-of-memory situations.
> 
> v3: -Use skb_try_coalesce, and revert to fraglist if this does not succeed.
>     -Make sure reassembly list head is uncloned.
> 
> v2: -Rebased on Ying's indentation fix.
>     -Node unlock call in msg_fragmenter case moved from patch #2 to #1.
>      ('continue' with this lock held would cause spinlock recursion if only
>       patch #1 is used)

This looks great, applied, thanks Erik.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html