From: "YOSHIFUJI Hideaki / 吉藤英明" <yoshfuji@linux-ipv6.org>
To: rmk@arm.linux.org.uk
Cc: linux-kernel@vger.kernel.org, linux-net@vger.kernel.org,
yoshfuji@linux-ipv6.org, davem@redhat.com
Subject: Re: IPv6 warnings
Date: Wed, 16 Jul 2003 20:07:28 +0900 (JST) [thread overview]
Message-ID: <20030716.200728.47761016.yoshfuji@linux-ipv6.org> (raw)
In-Reply-To: <20030716113657.A24009@flint.arm.linux.org.uk>
Hello.
In article <20030716113657.A24009@flint.arm.linux.org.uk> (at Wed, 16 Jul 2003 11:36:57 +0100), Russell King <rmk@arm.linux.org.uk> says:
> Linux version 2.6.0-test1 (src@tika) (gcc version 3.2.2 20030313
> (Red Hat Linux 3.2.2-10_rmk1)) #1280 Wed Jul 16 11:07:22 BST 2003
> CPU: StrongARM-1110 [6901b118] revision 8 (ARMv4)
>
> I'm running IPv6 the above, and I'm seeing the following messages.
> ipv6 was built as a module. Should I be worried?
>
> IPv6 v0.8 for NET4.0
> IPv6 over IPv4 tunneling driver
> Destroying alive neighbour c18c2a44
> [<c015bb84>] (dst_destroy+0x0/0x168) from [<bf00d024>] (ndisc_dst_gc+0x74/0xa4 [ipv6])
Please try this.
Index: linux-2.6/net/ipv6/route.c
===================================================================
RCS file: /home/cvs/linux-2.5/net/ipv6/route.c,v
retrieving revision 1.45
diff -u -r1.45 route.c
--- linux-2.6/net/ipv6/route.c 13 Jul 2003 06:12:30 -0000 1.45
+++ linux-2.6/net/ipv6/route.c 16 Jul 2003 09:44:39 -0000
@@ -567,6 +567,11 @@
if (unlikely(rt == NULL))
goto out;
+ if (dev)
+ dev_hold(dev);
+ if (neigh)
+ neigh_hold(neigh);
+
rt->rt6i_dev = dev;
rt->rt6i_nexthop = neigh;
rt->rt6i_expires = 0;
--
Hideaki YOSHIFUJI @ USAGI Project <yoshfuji@linux-ipv6.org>
GPG FP: 9022 65EB 1ECF 3AD1 0BDF 80D8 4807 F894 E062 0EEA
next prev parent reply other threads:[~2003-07-16 10:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-16 10:36 IPv6 warnings Russell King
2003-07-16 11:07 ` YOSHIFUJI Hideaki / 吉藤英明 [this message]
2003-07-16 12:36 ` David S. Miller
2003-07-16 12:50 ` Russell King
2003-07-16 11:11 ` Anders Gustafsson
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=20030716.200728.47761016.yoshfuji@linux-ipv6.org \
--to=yoshfuji@linux-ipv6.org \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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