Netdev List
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Denys Fedoryshchenko <denys@visp.net.lb>
Cc: netdev@vger.kernel.org
Subject: Re: BUG, 3.4.1, l2tp, kernel panic on rmmod l2tp_eth
Date: Thu, 07 Jun 2012 11:12:26 +0200	[thread overview]
Message-ID: <1339060346.26966.106.camel@edumazet-glaptop> (raw)
In-Reply-To: <61a2ca9cc47a9a9a1c8a36738090dbf9@visp.net.lb>

On Thu, 2012-06-07 at 11:31 +0300, Denys Fedoryshchenko wrote:
> Hi
> 
> Sorry for weird looking message, but this is how i got it over 
> netconsole
> 
> If i have any tunnel+session configured and up and will do rmmod 
> l2tp_eth,
> i will get panic, after my userspace program will fetch interfaces 
> information (over netlink).
> 
> Probably it should not rmmod if there is tunnels configured?

Sure, can you try the following patch ?

diff --git a/net/l2tp/l2tp_eth.c b/net/l2tp/l2tp_eth.c
index 443591d..185f12f 100644
--- a/net/l2tp/l2tp_eth.c
+++ b/net/l2tp/l2tp_eth.c
@@ -162,6 +162,7 @@ static void l2tp_eth_delete(struct l2tp_session *session)
 		if (dev) {
 			unregister_netdev(dev);
 			spriv->dev = NULL;
+			module_put(THIS_MODULE);
 		}
 	}
 }
@@ -249,6 +250,7 @@ static int l2tp_eth_create(struct net *net, u32 tunnel_id, u32 session_id, u32 p
 	if (rc < 0)
 		goto out_del_dev;
 
+	__module_get(THIS_MODULE);
 	/* Must be done after register_netdev() */
 	strlcpy(session->ifname, dev->name, IFNAMSIZ);
 

  reply	other threads:[~2012-06-07  9:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-07  8:31 BUG, 3.4.1, l2tp, kernel panic on rmmod l2tp_eth Denys Fedoryshchenko
2012-06-07  9:12 ` Eric Dumazet [this message]
2012-06-07  9:42   ` Denys Fedoryshchenko
2012-06-07 10:07     ` [PATCH] net: l2tp_eth: fix " Eric Dumazet
2012-06-07 20:02       ` David Miller

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=1339060346.26966.106.camel@edumazet-glaptop \
    --to=eric.dumazet@gmail.com \
    --cc=denys@visp.net.lb \
    --cc=netdev@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