[Top] [All Lists]

Re: Badness in dst_release

To: Jeff Garzik <jgarzik@xxxxxxxxx>
Subject: Re: Badness in dst_release
From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
Date: Sat, 18 Dec 2004 18:24:01 +1100
Cc: Netdev <netdev@xxxxxxxxxxx>, Arnaldo Carvalho de Melo <acme@xxxxxxxxxxxxxxxx>, YOSHIFUJI Hideaki / ???????????? <yoshfuji@xxxxxxxxxxxxxx>, "David S. Miller" <davem@xxxxxxxxxxxxx>
In-reply-to: <41C13D55.3070002@xxxxxxxxx>
References: <41C13D55.3070002@xxxxxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx
User-agent: Mutt/1.5.6+20040722i
On Thu, Dec 16, 2004 at 02:46:29AM -0500, Jeff Garzik wrote:
> 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.

Could you please check your kern.log for any abnormal messages prior
to this badness?

> 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.

Here's a check which might help.  Please apply it and see if it
produces anything.

BTW, there are still races left in addrconf.c.  However, they are
less likely to trigger compared to the one that's been fixed already.
The races are similar in nature to it.  For example, dad_complete
may race with dad_failure to lead to the sequence ip6_del_rt/ip6_ins_rt.

Visit Openswan at
Email: Herbert Xu ~{PmV>HI~} <herbert@xxxxxxxxxxxxxxxxxxx>
Home Page:
PGP Key:

Attachment: p
Description: Text document

<Prev in Thread] Current Thread [Next in Thread>