From: "David S. Miller" <davem@davemloft.net>
To: hadi@cyberus.ca
Cc: buytenh@wantstofly.org, yoshfuji@linux-ipv6.org,
jgarzik@pobox.com, netdev@oss.sgi.com
Subject: Re: BUG: dst underflow (again)
Date: Thu, 4 Nov 2004 22:18:01 -0800 [thread overview]
Message-ID: <20041104221801.584c8f11.davem@davemloft.net> (raw)
In-Reply-To: <1099577717.1039.155.camel@jzny.localdomain>
On 04 Nov 2004 09:15:17 -0500
jamal <hadi@cyberus.ca> wrote:
> Could you turn off netfilter and see if this continues to happen?
That's one possible angle, but let's look at the tracepoints
more closely.
BTW Lennert, the decoded addresses are extremely helpful. Thanks.
Jeff, could you similarly decode the ones that you seem to get?
That would be an incredibly useful datapoint. If you've provided
this already, my bad and please point me at where you posted that.
> > BUG: dst underflow -1: 3bcf9a80 at 42350024
> > BUG: dst underflow 0: 3bcf9a80 at 423486d2
> > BUG: dst underflow 0: 3bcf9a80 at 4235823d
...
> > 0x42350024 - 0x42345000 = 0xb024, corresponds to:
> > 0000affa <ip6_dst_check>
> >
> > 0x423486d2 - 0x42345000 = 0x36d2, corresponds to:
> > 0000339d <ip6_push_pending_frames>
> >
> > 0x4235823d - 0x42345000 = 0x1323d, corresponds to:
> > 00012c0d <udpv6_sendmsg> (god, that's one big function btw)
The last one is the most interesting. The only dst_release() call
that occurs in udpv6_sendmsg() is when xfrm_lookup() returns
an error. The semantics of that function are a complete mess
(when it errors, it sometimes releases the DST, sometimes does not)
and I'll fix that up.
But let me ask, do you have any IPSEC policies in the kernel
when these BUGs trigger? If so, I'm pretty sure I know what
the problem may be.
next prev parent reply other threads:[~2004-11-05 6:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-22 6:39 BUG: dst underflow (again) Jeff Garzik
2004-10-22 6:51 ` YOSHIFUJI Hideaki / 吉藤英明
2004-10-22 7:59 ` Lennert Buytenhek
2004-11-04 14:15 ` jamal
2004-11-05 6:18 ` David S. Miller [this message]
2004-11-05 6:53 ` YOSHIFUJI Hideaki / 吉藤英明
2004-11-05 7:16 ` David S. Miller
2004-11-05 7:44 ` YOSHIFUJI Hideaki / 吉藤英明
2004-11-05 7:05 ` Jeff Garzik
2004-11-05 7:14 ` David S. Miller
2004-11-05 7:34 ` Jeff Garzik
2004-11-05 7:38 ` Jeff Garzik
2004-11-05 9:13 ` Lennert Buytenhek
2004-11-05 9:14 ` Lennert Buytenhek
2004-11-05 9:42 ` Arnaldo Carvalho de Melo
[not found] ` <20041105101513.GA28779@xi.wantstofly.org>
2004-11-06 0:23 ` David S. Miller
2004-11-06 1:53 ` Herbert Xu
2004-11-06 9:02 ` Lennert Buytenhek
2004-11-06 8:17 ` Arnaldo Carvalho de Melo
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=20041104221801.584c8f11.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=buytenh@wantstofly.org \
--cc=hadi@cyberus.ca \
--cc=jgarzik@pobox.com \
--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 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).