From: Eric Dumazet <eric.dumazet@gmail.com>
To: Dave Jones <davej@redhat.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 19:31:18 +0200 [thread overview]
Message-ID: <1348507878.26828.1271.camel@edumazet-glaptop> (raw)
In-Reply-To: <20120924171152.GA26454@redhat.com>
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.
I guess your trinity tool gets better ?
I used following program to trigger the bug :
#include <sys/types.h>
#include <sys/socket.h>
#include <netinet/in.h>
#include <stdio.h>
#include <string.h>
int main(int argc, char *argv[])
{
int on = 1;
struct sockaddr_in addr;
int raw_sock = socket(AF_INET, SOCK_RAW, IPPROTO_TCP);
memset(&addr, 0, sizeof(addr));
addr.sin_family = AF_INET;
addr.sin_addr.s_addr = htonl(0x7f000001);
addr.sin_port = 123;
connect(raw_sock, (struct sockaddr *)&addr, sizeof(addr));
setsockopt(raw_sock, SOL_SOCKET, SO_KEEPALIVE, &on, sizeof(on));
return 0;
}
next prev parent reply other threads:[~2012-09-24 17:31 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 [this message]
2012-09-24 18:11 ` Dave Jones
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=1348507878.26828.1271.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=davej@redhat.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