From: Ralf Baechle <ralf@linux-mips.org>
To: Bernard Pidoux <bernard.pidoux@upmc.fr>
Cc: linux-hams <linux-hams@vger.kernel.org>
Subject: Re: Can AX25 socket debug message be removed ?
Date: Mon, 18 Jul 2011 16:17:41 +0100 [thread overview]
Message-ID: <20110718151740.GB5257@linux-mips.org> (raw)
In-Reply-To: <4E22E8FD.9000805@upmc.fr>
On Sun, Jul 17, 2011 at 03:51:57PM +0200, Bernard Pidoux wrote:
> I am actually concerned by two remaining bugs in ROSE module :
> First, is the occurence of negative values for neighbour->use parameter
> from time to time.
In the past week I noticed various ROSE bugs including non-atomic
manipulation of variables which may explain this and other issues. Some
may be hard to trigger but ROSE (and probably AX.25 and NETROM) are still
quite full of bugs.
> Second, is the impossibility to remove rose module after an application such
> as FPAC has initialized rose nodes and routes.
I never noticed that one - I tend to build my AX.25 test kernels with all
protocols and drivers built in most of the time.
Certain other kernel modules - IPv4 and IPv6 come to mind - cannot be
unloaded either. It was deemed to much work for too little gain to make
that work. I'm not sure if ROSE belongs into that group? Probably not.
Ralf
next prev parent reply other threads:[~2011-07-18 15:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-17 13:51 Can AX25 socket debug message be removed ? Bernard Pidoux
2011-07-18 15:17 ` Ralf Baechle [this message]
[not found] <4E22E1DD.2060902@upmc.fr>
2011-07-18 15:07 ` Ralf Baechle
2011-07-18 19:39 ` Bernard Pidoux
-- strict thread matches above, loose matches on Subject: below --
2010-12-02 12:05 [PATCH] [ROSE] AX25 packet routing improvement f6bvp
2010-12-21 10:38 ` Can AX25 socket debug message be removed ? f6bvp
2010-12-21 17:33 ` Ralf Baechle DL5RB
2010-12-22 9:43 ` Bernard Pidoux F6BVP
2011-02-15 14:25 ` f6bvp
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=20110718151740.GB5257@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=bernard.pidoux@upmc.fr \
--cc=linux-hams@vger.kernel.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