From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from relay.parallels.com ([195.214.232.42]:60647 "EHLO relay.parallels.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753108AbbFIPat (ORCPT ); Tue, 9 Jun 2015 11:30:49 -0400 Message-ID: <1433863846.23588.114.camel@odin.com> Subject: Re: Missed mainstream fix in 3.10 From: Kirill Tkhai To: Willy Tarreau CC: , Greg Kroah-Hartman Date: Tue, 9 Jun 2015 18:30:46 +0300 In-Reply-To: <20150609152340.GB9494@1wt.eu> References: <1433862928.23588.108.camel@odin.com> <20150609152340.GB9494@1wt.eu> Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: stable-owner@vger.kernel.org List-ID: В Вт, 09/06/2015 в 17:23 +0200, Willy Tarreau пишет: > Hi, > > On Tue, Jun 09, 2015 at 06:15:28PM +0300, Kirill Tkhai wrote: > > Hi, > > > > it looks like the bellow commit is missed in stable 3.10 kernel. > > In 2.6.32 without this commit we observed a bridge dropping big > > packets. The fix is in mainstream kernel now. > > Please, look if it's need in stable 3.10 kernel. > > > > commit aff09ce303f83bd370772349238482ae422a2341 > > Author: Vasily Averin > > Date: Mon May 5 00:17:48 2014 +0400 > > > > bridge: superfluous skb->nfct check in br_nf_dev_queue_xmit > > > (...) > > But this patch is not in 2.6.32 either. Does this mean you applied it to > your own tree, in which case it should have been backported to all kernels > from 2.6.32 to 3.14 as well (since it was merged in 3.15) ? That's a bit > confusing. It was applied to our local 2.6.32 kernel tree and was commited to upstream. We didn't trace if it was commited to stable trees. Now I'm porting some local patches from 2.6.32 to 3.10 and found that this patch isn't in stable 3.10. So I'm reporting to stable tree guys. > Anyway anything related to network should pass via netdev.