From: Jeff Garzik <jgarzik@pobox.com>
To: Netdev <netdev@oss.sgi.com>
Cc: "Herbert Xu" <herbert@gondor.apana.org.au>,
"Arnaldo Carvalho de Melo" <acme@conectiva.com.br>,
"YOSHIFUJI Hideaki / 吉藤英明" <yoshfuji@linux-ipv6.org>,
"David S. Miller" <davem@davemloft.net>
Subject: Badness in dst_release
Date: Thu, 16 Dec 2004 02:46:29 -0500 [thread overview]
Message-ID: <41C13D55.3070002@pobox.com> (raw)
After a week or more of uptime, the "Badness in dst_release" messages
started again. Kernel 2.6.10-rc3-bk2. The first message is below.
Arnaldo and Yoshifuji should have already have access to this machine
(although I just rebooted into -bk-latest)
IMO, if you want additional debugging code, add some non-intrusive
checks in the upstream kernel. Since this problem doesn't appear for a
while, additional checks would be useful.
Badness in dst_release at include/net/dst.h:149
[<f8c1124d>] ip6_dst_check+0x64/0x6a [ipv6]
[<f8c080da>] ip6_dst_lookup+0x1a7/0x1c1 [ipv6]
[<f8c1a4e6>] udpv6_sendmsg+0x297/0x931 [ipv6]
[<c03194ef>] udp_recvmsg+0x60/0x2e9
[<c032086d>] inet_sendmsg+0x4d/0x59
[<c02d33d8>] sock_sendmsg+0xe8/0x103
[<c011bb37>] find_busiest_group+0xcf/0x2db
[<c011bfb9>] load_balance_newidle+0x36/0xb4
[<c01ec15c>] copy_from_user+0x42/0x6e
[<c0133fd2>] autoremove_wake_function+0x0/0x57
[<c02d4cf6>] sys_sendmsg+0x189/0x1e6
[<c0355e24>] schedule_timeout+0xbd/0xbf
[<c0134a47>] unqueue_me+0x5a/0xa5
[<c0133dda>] add_wait_queue+0x1a/0x46
[<c0134be4>] futex_wait+0x152/0x170
[<c014ecd4>] find_extend_vma+0x29/0x7e
[<c011c7d5>] default_wake_function+0x0/0x12
[<c01346e0>] futex_wake+0x74/0xc4
[<c01ec15c>] copy_from_user+0x42/0x6e
[<c02d5180>] sys_socketcall+0x236/0x254
[<c0102f0d>] sysenter_past_esp+0x52/0x71
next reply other threads:[~2004-12-16 7:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-16 7:46 Jeff Garzik [this message]
2004-12-18 7:24 ` Badness in dst_release Herbert Xu
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=41C13D55.3070002@pobox.com \
--to=jgarzik@pobox.com \
--cc=acme@conectiva.com.br \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=netdev@oss.sgi.com \
--cc=yoshfuji@linux-ipv6.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.