From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262529AbTJYJbN (ORCPT ); Sat, 25 Oct 2003 05:31:13 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262539AbTJYJbN (ORCPT ); Sat, 25 Oct 2003 05:31:13 -0400 Received: from louise.pinerecords.com ([213.168.176.16]:6349 "EHLO louise.pinerecords.com") by vger.kernel.org with ESMTP id S262529AbTJYJbL (ORCPT ); Sat, 25 Oct 2003 05:31:11 -0400 Date: Sat, 25 Oct 2003 11:12:56 +0200 From: Tomas Szepe To: "David S. Miller" Cc: linux-kernel@vger.kernel.org, netdev@oss.sgi.com, grof@dragon.cz Subject: Re: possible bug in tcp_input.c Message-ID: <20031025091256.GB13378@louise.pinerecords.com> References: <20031024162959.GB11154@louise.pinerecords.com> <20031024193034.30f1caed.davem@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20031024193034.30f1caed.davem@redhat.com> User-Agent: Mutt/1.4.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Oct-24 2003, Fri, 19:30 -0700 David S. Miller wrote: > > /* tcp_input.c, line 1138 */ > > static inline int tcp_head_timedout(struct sock *sk, struct tcp_opt *tp) > > { > > return tp->packets_out && tcp_skb_timedout(tp, skb_peek(&sk->write_queue)); > > } > > > > The passed NULL (and yes, this is where we are getting one) is dereferenced > > immediately in: > > > > /* tcp_input.c, line 1133 */ > > static inline int tcp_skb_timedout(struct tcp_opt *tp, struct sk_buff *skb) > > { > > return (tcp_time_stamp - TCP_SKB_CB(skb)->when > tp->rto); > > } > > If tp->packets_out is non-zero (which by definition it is > in your case else the right hand side of the "&&" would not be > evaluated) then we _MUST_ have some packets in sk->write_queue. > > Something is being fiercely corrupted. Probably some piece of > netfilter is freeing up an SKB one too many times thus corrupting > the TCP write queue list pointers. Ok, thanks. Here's the backtrace in case you are able to extract some information out of it. >>EIP; c01fa86f <===== >>ebx; c606c19c <_end+5d94b7c/85faa40> >>esi; c606c0e0 <_end+5d94ac0/85faa40> >>ebp; c606c0e0 <_end+5d94ac0/85faa40> >>esp; c026bc24 Trace; c01ffbe5 Trace; c01fb46b Trace; c01fbc67 Trace; c01fc06c Trace; c01fe6f2 Trace; c88e3c34 <[ip_tables]__kstrtab_ipt_register_table+0/0> Trace; c01063a2 Trace; c0206835 Trace; c01ed38e Trace; c01e0a3b Trace; c01ed240 Trace; c01ed008 Trace; c01ed240 Trace; c01ed589 Trace; c8912ddc <.data.end+3ba5/????> Trace; c01e0ca4 Trace; c01ed3b0 Trace; c88fa12a <[ip_nat_ftp].data.end+184b/8781> Trace; c01e21cd Trace; c88fa1cf <[ip_nat_ftp].data.end+18f0/8781> Trace; c01e08c2 Trace; c88fa7c0 <[ip_nat_ftp].data.end+1ee1/8781> Trace; c01ed3b0 Trace; c01ed3b0 Trace; c01e0a97 Trace; c88fa7a0 <[ip_nat_ftp].data.end+1ec1/8781> Trace; c01ed3b0 Trace; c88fa7c0 <[ip_nat_ftp].data.end+1ee1/8781> Trace; c01ed1de Trace; c01ed3b0 Trace; c01da3ef Trace; c01da533 Trace; c01da644 Trace; c011b3b5 Trace; c0108b4a Trace; c0105390 Trace; c010b0a8 Trace; c0105390 Trace; c01053b3 Trace; c0105442 Trace; c0105000 <_stext+0/0> -- Tomas Szepe