From: "David S. Miller" <davem@davemloft.net>
To: Duncan Sands <baldrick@free.fr>
Cc: linux-kernel@vger.kernel.org, netdev@oss.sgi.com, laforge@gnumonks.org
Subject: Re: Oops at __neigh_for_each_release (2.6.9-rc3)
Date: Fri, 1 Oct 2004 13:56:36 -0700 [thread overview]
Message-ID: <20041001135636.0c071602.davem@davemloft.net> (raw)
In-Reply-To: <200410012217.35264.baldrick@free.fr>
On Fri, 1 Oct 2004 22:17:35 +0200
Duncan Sands <baldrick@free.fr> wrote:
> EIP is at __neigh_for_each_release+0x32/0xb0
Give this patch a try. And please report networking bugs
to netdev@oss.sgi.com in the future, thanks.
===== net/atm/clip.c 1.42 vs edited =====
--- 1.42/net/atm/clip.c 2004-09-23 18:02:32 -07:00
+++ edited/net/atm/clip.c 2004-10-01 13:35:40 -07:00
@@ -984,19 +984,7 @@
static int __init atm_clip_init(void)
{
- /* we should use neigh_table_init() */
- clip_tbl.lock = RW_LOCK_UNLOCKED;
- clip_tbl.kmem_cachep = kmem_cache_create(clip_tbl.id,
- clip_tbl.entry_size, 0, SLAB_HWCACHE_ALIGN, NULL, NULL);
-
- if (!clip_tbl.kmem_cachep)
- return -ENOMEM;
-
- /* so neigh_ifdown() doesn't complain */
- clip_tbl.proxy_timer.data = 0;
- clip_tbl.proxy_timer.function = NULL;
- init_timer(&clip_tbl.proxy_timer);
- skb_queue_head_init(&clip_tbl.proxy_queue);
+ neigh_table_init(&clip_tbl);
clip_tbl_hook = &clip_tbl;
register_atm_ioctl(&clip_ioctl_ops);
@@ -1022,7 +1010,6 @@
deregister_atm_ioctl(&clip_ioctl_ops);
- neigh_ifdown(&clip_tbl, NULL);
dev = clip_devs;
while (dev) {
next = PRIV(dev)->next;
@@ -1030,9 +1017,11 @@
free_netdev(dev);
dev = next;
}
- if (start_timer == 0) del_timer(&idle_timer);
- kmem_cache_destroy(clip_tbl.kmem_cachep);
+ neigh_table_clear(&clip_tbl);
+
+ if (start_timer == 0)
+ del_timer(&idle_timer);
clip_tbl_hook = NULL;
}
next parent reply other threads:[~2004-10-01 20:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200410012217.35264.baldrick@free.fr>
2004-10-01 20:56 ` David S. Miller [this message]
2004-10-02 7:58 ` Oops at __neigh_for_each_release (2.6.9-rc3) Duncan Sands
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=20041001135636.0c071602.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=baldrick@free.fr \
--cc=laforge@gnumonks.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
/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).