netdev - Re: [XFRM]: beet: fix worst case header

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 for Android: free password hash cracker in your pocket

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

Message-Id: <20070409.114840.18284797.davem@davemloft.net>
Date:	Mon, 09 Apr 2007 11:48:40 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	kaber@...sh.net
Cc:	netdev@...r.kernel.org
Subject: Re: [XFRM]: beet: fix worst case header_len calculation

From: Patrick McHardy <kaber@...sh.net>
Date: Sun, 08 Apr 2007 04:56:51 +0200

> The pskb_copy_expand crash I was seeing was triggered by BEET
> mode not calculating the SA's header_len value for the worst
> case, causing skb headroom expansions. This patch uses the
> worst case value by including the maximum length of the pseudo
> header.
> 
> The patch applies on top of the MTU optimization patch.

Applied, thanks Patrick.

Can you backport this to 2.6.21 for me, if you think we should
bother?  Thanks.

-
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