netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@davemloft.net>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: hadi@cyberus.ca, buytenh@wantstofly.org, yoshfuji@linux-ipv6.org,
	netdev@oss.sgi.com
Subject: Re: BUG: dst underflow (again)
Date: Thu, 4 Nov 2004 23:14:33 -0800	[thread overview]
Message-ID: <20041104231433.3a7233e8.davem@davemloft.net> (raw)
In-Reply-To: <418B2645.6080404@pobox.com>

On Fri, 05 Nov 2004 02:05:41 -0500
Jeff Garzik <jgarzik@pobox.com> wrote:

> David S. Miller wrote:
> > 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.
> 
> I've compiled IPv6 into my router's kernel image, so next time I reboot, 
> I should be able to get at symbol info out of the BUGs a bit more easily.

Thanks a lot.

> > 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.
> 
> I know this question wasn't directed at me, but, I do always compile 
> ipsec stuff into my kernel, in addition to netfilter.  The relevant 
> options are attached for the curious.

Yes, but do you actually install any IPSEC rules into your system?

The only way xfrm_lookup() can ever fall (and call that BUG'ing
dst_release() in udpv6_sendmsg()) is if you have at least some
IPSEC policies configured.

  reply	other threads:[~2004-11-05  7:14 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
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 [this message]
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=20041104231433.3a7233e8.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).