From: Ralf Baechle <ralf@linux-mips.org>
To: Bernard F6BVP <f6bvp@free.fr>
Cc: wchast@gmail.com, davem@davemloft.net, linux-hams@vger.kernel.org
Subject: Re: instant oops with AF_ROSE
Date: Wed, 20 Jul 2011 10:32:14 +0100 [thread overview]
Message-ID: <20110720093214.GA20152@linux-mips.org> (raw)
In-Reply-To: <4E186E25.5080200@free.fr>
On Sat, Jul 09, 2011 at 05:05:09PM +0200, Bernard F6BVP wrote:
> What we do with ROSE nodes is to create a network allowing AX25
> frames routing based on destination address. However, basically,
> ROSE frames
> are still AX.25 standard frames that can be sent over packet radio.
> In order to relay rose frames through Internet, applications like
> ax25ipd encapsulates rose inside of IP or UDP frames.
>
> I agree that rose module is still unfriendly and will crash linux
> kernel on some occasions.
> For example, after creating rose socket and populating rose routing
> table, removing rose module is not possible.
>
> There is either a kernel crash or a looping message
>
> kernel:unregister_netdevice: waiting for rose0 to become free. Usage
> count = 6
>
> where count can be any number without any relation to actual usage
> and remaining the same, preventing Linux to shutdown.
>
> I noticed that there are no refcount entries in rose node or rose neigh
> structures. This may be related ?
As part of fixing the problem reported by David I've found 4 race conditions
so far. I've posted the patches to linux-hams for testing but on a 2nd
thought I think the race accessing rose_neigh->use is unlikely to be the
cause for what Bernard is observing.
Ralf
next prev parent reply other threads:[~2011-07-20 9:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-09 15:05 instant oops with AF_ROSE Bernard F6BVP
2011-07-20 9:32 ` Ralf Baechle [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-07-06 10:57 David Miller
2011-07-06 11:42 ` Chuck Hast
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=20110720093214.GA20152@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=davem@davemloft.net \
--cc=f6bvp@free.fr \
--cc=linux-hams@vger.kernel.org \
--cc=wchast@gmail.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