From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeff Garzik Subject: Badness in dst_release Date: Thu, 16 Dec 2004 02:46:29 -0500 Message-ID: <41C13D55.3070002@pobox.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: Herbert Xu , Arnaldo Carvalho de Melo , =?UTF-8?B?WU9TSElGVUpJIEhpZGVha2kgLyDlkInol6Toi7HmmI4=?= , "David S. Miller" Return-path: To: Netdev Sender: netdev-bounce@oss.sgi.com Errors-to: netdev-bounce@oss.sgi.com List-Id: netdev.vger.kernel.org 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 [] ip6_dst_check+0x64/0x6a [ipv6] [] ip6_dst_lookup+0x1a7/0x1c1 [ipv6] [] udpv6_sendmsg+0x297/0x931 [ipv6] [] udp_recvmsg+0x60/0x2e9 [] inet_sendmsg+0x4d/0x59 [] sock_sendmsg+0xe8/0x103 [] find_busiest_group+0xcf/0x2db [] load_balance_newidle+0x36/0xb4 [] copy_from_user+0x42/0x6e [] autoremove_wake_function+0x0/0x57 [] sys_sendmsg+0x189/0x1e6 [] schedule_timeout+0xbd/0xbf [] unqueue_me+0x5a/0xa5 [] add_wait_queue+0x1a/0x46 [] futex_wait+0x152/0x170 [] find_extend_vma+0x29/0x7e [] default_wake_function+0x0/0x12 [] futex_wake+0x74/0xc4 [] copy_from_user+0x42/0x6e [] sys_socketcall+0x236/0x254 [] sysenter_past_esp+0x52/0x71