From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dave Jones Subject: Re: kernel BUG at kernel/timer.c:748! Date: Mon, 24 Sep 2012 11:39:21 -0400 Message-ID: <20120924153921.GA13845@redhat.com> References: <20120905043523.GA12988@redhat.com> <20120914212958.GA25053@redhat.com> <20120919211059.GA10985@redhat.com> <1348092082.31352.51.camel@edumazet-glaptop> <20120920020223.GA28110@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Yuchung Cheng , Julian Anastasov , netdev@vger.kernel.org To: Eric Dumazet Return-path: Received: from mx1.redhat.com ([209.132.183.28]:3987 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756546Ab2IXPjg (ORCPT ); Mon, 24 Sep 2012 11:39:36 -0400 Content-Disposition: inline In-Reply-To: <20120920020223.GA28110@redhat.com> Sender: netdev-owner@vger.kernel.org List-ID: On Wed, Sep 19, 2012 at 10:02:23PM -0400, Dave Jones wrote: > On Thu, Sep 20, 2012 at 12:01:22AM +0200, Eric Dumazet wrote: > > > I spent some time trying to track this bug, but found nothing so far. > > > > The timer->function are never cleared by TCP stack at tear down, and > > should be set before fd is installed and can be caught by other threads. > > > > Most likely its a refcounting issue... > > > > Following debugging patch might trigger a bug sooner ? > > 4 hours so far, nothing.. I'll leave it run overnight, but it doesn't seem to have > made much difference if any. One of my over-weekend runs hit this again, but it didn't trigger the WARN that your patch added :-/ Dave