All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Bernard f6bvp <f6bvp@free.fr>
Cc: duoming@zju.edu.cn, davem@davemloft.net, edumazet@google.com,
	linux-hams@vger.kernel.org, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org, pabeni@redhat.com, ralf@linux-mips.org
Subject: Re: [PATCH] net: rose: fix unregistered netdevice: waiting for rose0 to become free
Date: Fri, 15 Jul 2022 15:43:14 -0700	[thread overview]
Message-ID: <20220715154314.510ca2fb@kernel.org> (raw)
In-Reply-To: <ab0eac7b-3041-6772-21dd-273e1b8fc43e@free.fr>

On Fri, 15 Jul 2022 17:59:06 +0200 Bernard f6bvp wrote:
> Here is the context.
> 
> This patch adds dev_put(dev) in order to allow removal of rose module 
> after use of AX25 and ROSE via rose0 device.
> 
> Otherwise when trying to remove rose module via rmmod rose an infinite 
> loop message was displayed on all consoles with xx being a random number.
> 
> unregistered_netdevice: waiting for rose0 to become free. Usage count = xx
> 
> unregistered_netdevice: waiting for rose0 to become free. Usage count = xx
> 
> ...
> 
> With the patch it is ok to rmmod rose.
> 
> This bug appeared with kernel 4.10 and was tentatively repaired five 
> years ago.

Please try resending with git send-email.
Your current email contains HTML so it won't make it to netdev@
and other vger lists.

> *Subject: [BUG] unregistered netdevice: wainting for rose0 to become 
> free. Usage count = xx <https://marc.info/?t=148811830800001&r=1&w=2> 
> From: f6bvp <f6bvp () free ! fr> 
> <https://marc.info/?a=128152583500001&r=1&w=2> Date: 2017-02-26 14:09:08 
> <https://marc.info/?l=linux-hams&r=1&w=2&b=201702> Message-ID: 
> ce03a972-a3b0-ca24-5195-2fe2fd5c44d3 () free ! fr 
> <https://marc.info/?i=ce03a972-a3b0-ca24-5195-2fe2fd5c44d3%20()%20free%20!%20fr>* 
> 
> 
> Since then the bug reamains.

Is it possible to use a link to the lore.kernel.org archive? It's the
most common way of referring to past threads these days.

> Signed-off-by: Bernard f6bvp / ai7bg

Well formed s-o-b is required, "the name you'd use if you were signing
a legal document".

> diff --git a/a/net/rose/af_rose.c b/b/net/rose/af_rose.c
> index bf2d986..41e106a 100644
> --- a/a/net/rose/af_rose.c
> +++ b/b/net/rose/af_rose.c
> @@ -711,6 +711,7 @@ static int rose_bind(struct socket *sock, struct 
> sockaddr *uaddr, int addr_len)
>          rose_insert_socket(sk);
> 
>          sock_reset_flag(sk, SOCK_ZAPPED);
> +       dev_put(dev);
> 
>          return 0;
>   }

  parent reply	other threads:[~2022-07-15 22:43 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-11  1:31 [PATCH net v6] net: rose: fix null-ptr-deref caused by rose_kill_by_neigh Duoming Zhou
2022-07-12 11:00 ` Paolo Abeni
2022-07-13  7:50   ` duoming
2022-07-13  8:33     ` Paolo Abeni
2022-07-13  9:03       ` duoming
2022-07-14 14:11         ` Bernard f6bvp
2022-07-14 14:23           ` Dan Carpenter
     [not found]           ` <ab0eac7b-3041-6772-21dd-273e1b8fc43e@free.fr>
2022-07-15 22:43             ` Jakub Kicinski [this message]
2022-07-22 16:41               ` [PATCH] net: rose: fix unregistered netdevice: waiting for rose0 to become free Bernard f6bvp
2022-07-22 17:05                 ` Eric Dumazet
2022-07-23  9:55                   ` Bernard f6bvp
2022-07-23 11:21                   ` Bernard F6BVP
2022-07-26 13:44                     ` Eric Dumazet
2022-07-22 17:37                 ` Jakub Kicinski
2022-07-26 18:25                   ` [PATCH 1/1] " Bernard Pidoux
2022-07-27  9:06                     ` Eric Dumazet
2022-09-04 22:48                       ` 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=20220715154314.510ca2fb@kernel.org \
    --to=kuba@kernel.org \
    --cc=davem@davemloft.net \
    --cc=duoming@zju.edu.cn \
    --cc=edumazet@google.com \
    --cc=f6bvp@free.fr \
    --cc=linux-hams@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=ralf@linux-mips.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.