From: Dave Jones <davej@redhat.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Yuchung Cheng <ycheng@google.com>, Julian Anastasov <ja@ssi.bg>,
netdev@vger.kernel.org
Subject: Re: kernel BUG at kernel/timer.c:748!
Date: Mon, 24 Sep 2012 14:11:52 -0400 [thread overview]
Message-ID: <20120924181152.GA31183@redhat.com> (raw)
In-Reply-To: <1348507878.26828.1271.camel@edumazet-glaptop>
On Mon, Sep 24, 2012 at 07:31:18PM +0200, Eric Dumazet wrote:
> On Mon, 2012-09-24 at 13:11 -0400, Dave Jones wrote:
>
> > Great, I'll give this a shot.
> >
> > Any idea why this only just started triggering ?
> > (Ie, do we need this for stable too?)
>
> Seems this is a very old bug.
Indeed. As far as I can tell, this goes back to 2.1.8,
back in November 1996.
> I guess your trinity tool gets better ?
Possible. Or it may be that it was finding other bugs first
that are now fixed, that prevented us getting far enough along
to try this.
> I used following program to trigger the bug :
I'm sure reproducers like that will be appreciated by anyone
running QA tests on older kernels.
tangent: Is there any kind of networking correctness suite
other than fuzz testers like isic etc ?
thanks,
Dave
next prev parent reply other threads:[~2012-09-24 18:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-05 4:35 kernel BUG at kernel/timer.c:748! Dave Jones
2012-09-05 16:04 ` Lin Ming
2012-09-05 16:37 ` Yuchung Cheng
2012-09-05 17:08 ` Dave Jones
2012-09-05 21:18 ` Jerry Chu
2012-09-05 20:48 ` Julian Anastasov
2012-09-14 21:29 ` Dave Jones
2012-09-15 18:16 ` Yuchung Cheng
2012-09-19 21:10 ` Dave Jones
2012-09-19 22:01 ` Eric Dumazet
2012-09-20 2:02 ` Dave Jones
2012-09-24 15:39 ` Dave Jones
2012-09-24 16:34 ` Eric Dumazet
2012-09-24 17:00 ` Eric Dumazet
2012-09-24 17:11 ` Dave Jones
2012-09-24 17:31 ` Eric Dumazet
2012-09-24 18:11 ` Dave Jones [this message]
2012-09-24 20:53 ` David Miller
2012-09-24 20:53 ` David Miller
2012-09-24 21:01 ` Eric Dumazet
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120924181152.GA31183@redhat.com \
--to=davej@redhat.com \
--cc=eric.dumazet@gmail.com \
--cc=ja@ssi.bg \
--cc=netdev@vger.kernel.org \
--cc=ycheng@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).