[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0911032330090.3488@melkinkari.cs.Helsinki.FI>
Date: Tue, 3 Nov 2009 23:34:19 +0200 (EET)
From: "Ilpo JÀrvinen" <ilpo.jarvinen@...sinki.fi>
To: Gilad Ben-Yossef <gilad@...efidence.com>
cc: Valdis.Kletnieks@...edu, Eric Dumazet <eric.dumazet@...il.com>,
Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
Ori Finkelman <ori@...sleep.com>
Subject: Re: 2.6.32-rc5-mmotm1101 - kernel BUG at net/ipv4/tcp_input.c:3707!
On Tue, 3 Nov 2009, Gilad Ben-Yossef wrote:
> Eric Dumazet wrote:
>
> > Valdis.Kletnieks@...edu a écrit :
> >
> > > Seen right after I started 'fetchmail'. Reproducible - 3 out of 3.
> > > I'll bisect this tonight if nobody jumps up and yells they know what it
> > > is...
> > >
> Bah... this is most probably my fault. Sorry about that.
>
> Can you please try the patch in the next email?
>
> But also, can you please send me the route table in effect when this happened
> and the fetchmail command line/config (removing any passwords or account
> details of course)? I want to understand better when this happens.
According to the stacktrace, it came from ipv6 side which doesn't have any
null checking what so ever atm (you only handled ipv4 correctly). ...You
should be a bit more careful next time when adding any BUG_ONs...
--
i.
Powered by blists - more mailing lists