Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 11 Apr 2001 14:25:40 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 11 Apr 2001 14:25:20 -0400 Received: from ns.suse.de ([213.95.15.193]:64267 "HELO Cantor.suse.de") by vger.kernel.org with SMTP id ; Wed, 11 Apr 2001 14:25:18 -0400 Date: Wed, 11 Apr 2001 20:25:12 +0200 From: Andi Kleen To: Bart Trojanowski Cc: Imran.Patel@nokia.com, ak@suse.de, netfilter-devel@us5.samba.org, netdev@oss.sgi.com, LKML Subject: Re: skb allocation problems (More Brain damage!) Message-ID: <20010411202512.A15011@gruyere.muc.suse.de> In-Reply-To: <2D6CADE9B0C6D411A27500508BB3CBD063CF2D@eseis15nok> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from bart@jukie.net on Wed, Apr 11, 2001 at 01:47:18PM -0400 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Apr 11, 2001 at 01:47:18PM -0400, Bart Trojanowski wrote: > > Coudl the problem be in the NIC driver not in the alloc_skb? I have used > both 2.4.{1,3} for some time and never seen this corruption. I use ping > -f with various packet sizes for stress testing my IPSec boxes... these do > quite a bit of extra skb creation as an IPSec header sometimes does not > fit in the original skb. No problems yet. > > My gut tells me to blame the NIC driver of the NIC itself. The NIC is not directly involved in alloc_skb() (except maybe if it corrupts internal data structures of the allocator) -Andi - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/