From: Jean Tourrilhes <jt@bougret.hpl.hp.com>
To: Martin Diehl <lists@mdiehl.de>
Cc: Pawel Kot <pkot@linuxnews.pl>, Dag Brattli <dagb@cs.uit.no>,
linux-kernel@vger.kernel.org, linux-irda@pasta.cs.uit.no
Subject: Re: [BUG()] IrDA in 2.4.16 + preempt
Date: Mon, 17 Dec 2001 14:45:49 -0800 [thread overview]
Message-ID: <20011217144549.B3647@bougret.hpl.hp.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0112141128300.662-100000@urtica.linuxnews.pl> <Pine.LNX.4.21.0112161338110.444-100000@notebook.diehl.home>
In-Reply-To: <Pine.LNX.4.21.0112161338110.444-100000@notebook.diehl.home>; from lists@mdiehl.de on Mon, Dec 17, 2001 at 10:28:45AM +0100
On Mon, Dec 17, 2001 at 10:28:45AM +0100, Martin Diehl wrote:
>
> [Jean added to CC]
>
> On Fri, 14 Dec 2001, Pawel Kot wrote:
>
> > I found an annoying problem with irda on 2.4.16.
> > When I remove irlan module I get sementation fault:
> > root@blurp:~# rmmod irlan
> > Dec 14 02:27:35 blurp kernel: kernel BUG at slab.c:1200!
> > Dec 14 02:27:35 blurp kernel: invalid operand: 0000
> > Dec 14 02:27:35 blurp kernel: CPU: 0
> > Dec 14 02:27:35 blurp kernel: EIP: 0010:[kmem_extra_free_checks+81/140] Not tainted
> [...]
> > Dec 14 02:27:35 blurp kernel: Process rmmod (pid: 110, stackpage=cc045000)
> [..]
> > Dec 14 02:27:35 blurp kernel: Call Trace:
Where is this comming from ? Was it sent to the IrDA mailing list ?
> [kfree+450/576]
> [netdev_finish_unregister+145/152]
> [unregister_netdevice+451/632]
> [unregister_netdev+16/40]
>
> Seems some inconsistency in the way how the irlan netdev is handled:
> having NETIF_F_DYNALLOC set for a netdev which is not allocated as an
> independent object doesn't seem to be a good idea to me ;-)
>
> The patch below simply removes NETIF_F_DYNALLOC just before calling
> unregister_netdev() und should fix the issue. It's untested however,
> since I'm unable to reproduce the Oops on UP without preempt (but it
> should be there as well, due to ipfrag_time for example). At least it
> compiles and doesn't do any harm to me.
Why don't you just fix irlan_eth_init() ? The NETIF_F_DYNALLOC
is only used in the unregister_netdevice() functions (check your
kernel), so it's cleaner to never set the flag in the first place.
Also : I suspect the Dag added this flag as a workaround for
some refcount problem, because with it the code does one more unref
that without. So, I suspect the refcount is broken. By the way, this
flag doesn't change the behaviour as far as waiting for people that
hold some refcount on the device.
> IMHO, retiring dynalloc is just some sort of band-aid because I do
> believe, using it would be a good idea - but would need some more
> changes for irlan.
No, that the right way. NETIF_F_DYNALLOC is only ever used for
that. One the other hand, you might need to fix the refcount.
> Btw., I'm not sure about the status of irlan - I'm only using ppp over
> ircomm or irnet.
Same for me.
> HTH
> Martin
Have fun...
Jean
next prev parent reply other threads:[~2001-12-17 22:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-14 10:31 Pawel Kot
2001-12-17 9:28 ` Martin Diehl
2001-12-17 22:20 ` Pawel Kot
2001-12-17 23:19 ` Pawel Kot
2001-12-17 22:45 ` Jean Tourrilhes [this message]
2001-12-17 23:22 ` Pawel Kot
2001-12-18 0:10 ` Jean Tourrilhes
2001-12-18 0:22 ` Pawel Kot
2001-12-18 1:16 ` Pawel Kot
2001-12-18 1:23 ` Jean Tourrilhes
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=20011217144549.B3647@bougret.hpl.hp.com \
--to=jt@bougret.hpl.hp.com \
--cc=dagb@cs.uit.no \
--cc=jt@hpl.hp.com \
--cc=linux-irda@pasta.cs.uit.no \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@mdiehl.de \
--cc=pkot@linuxnews.pl \
/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
all inboxes | Powered by JetHome®