Netdev List
 help / color / mirror / Atom feed
From: f6bvp <f6bvp@free.fr>
To: netdev@vger.kernel.org, linux-hams@vger.kernel.org
Cc: dvyukov@google.com, richard@rns-stearn.co.uk,
	thomas@osterried.de, f6bvp@amsat.org
Subject: [ROSE] Bug : waiting for rose module to become free
Date: Sat, 16 Feb 2019 19:44:23 +0100	[thread overview]
Message-ID: <20190216194423.3727d498@draws-f6bvp> (raw)

Hi,
A nastly bug is still pending in ROSE module that prevents it to be removed.
When trying to remove rose module we enter into an endless loop with displayed message :
 "waiting for rose module to become free"
A patch from Richard Stern had been committed a while ago but it did not get a chance to be applied.

https://marc.info/?l=linux-hams&m=150870350516064&w=2

Since then, there have been some changes in af_rose.c and net code architecture that prevents simply adding missing dev_put(dev) in present kernel.

From time to time we can observe a negative count (-1 for integer value is displayed as 65535 in /proc/net/rose_neigh) that probably means there is a bug in rose module refcount (??).

/proc/net/rose_neigh
00015 SV1HCC-9  ax0      2   1  DCE     yes   0   0
00013 PE1OWG-11 ax0      2 65535  DCE     yes   0   0
00011 F5KTR-11  ax0      1   1  DCE     yes   0   0
00007 F3KT-11   ax0      2   1  DCE     yes   0   0
00003 SK7ES-9   ax0      2   1  DTE     yes   0   0
00002 K4GBB-9   ax0      4   0  DCE     yes   0   0
00001 RSLOOP-0  ???      1   2  DCE     yes   0   0

Help is kindly requested to get a valid patch.

Bernard, 
f6bvp



                 reply	other threads:[~2019-02-16 18:44 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20190216194423.3727d498@draws-f6bvp \
    --to=f6bvp@free.fr \
    --cc=dvyukov@google.com \
    --cc=f6bvp@amsat.org \
    --cc=linux-hams@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=richard@rns-stearn.co.uk \
    --cc=thomas@osterried.de \
    /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