On Fri, Feb 10, 2012 at 02:38:42AM -0500, David Miller wrote:
> From: Eric Dumazet <[email protected]>
> Date: Fri, 10 Feb 2012 07:53:33 +0100
> 
> > Le vendredi 10 février 2012 à 12:48 +0800, 单卫 a écrit :
> >> Latest 2.6.32 stable tree(56) still has same problem. 
> >> 
> >> 
> >> The following two commit should not be queued to 2.6.32?
> >> 
> >> b1faf5666438090a4dc4fceac8502edc7788b7e3
> >> (net: sock_queue_err_skb() dont mess with sk_forward_alloc)
> >> 
> >> 2903037400a26e7c0cc93ab75a7d62abfacdf485
> >> (net: fix sk_forward_alloc corruptions) 
> >> 
> > 
> > You're right, please Greg, here is the backported patch for 2.6.32.56,
> > once David agreed.
> > 
> > Thanks !
> > 
> > [PATCH] net: sock_queue_err_skb() dont mess with sk_forward_alloc)
> > 
> > Upstream commit b1faf5666438090a4dc4fceac8502edc7788b7e3 (2.6.35)
> > 
> > Depending on commit 2903037400a26e7c0cc93ab75a7d62abfacdf485
> > (net: fix sk_forward_alloc corruptions) 
> > 
> > Signed-off-by: Eric Dumazet <[email protected]>
> 
> Acked-by: David S. Miller <[email protected]>

Now applied, thanks.

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to