From: David Miller <davem@davemloft.net>
To: nicolas.dichtel@6wind.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next 1/4] ipip: allow to deactivate the creation of fb dev
Date: Mon, 19 Nov 2012 19:06:48 -0500 (EST) [thread overview]
Message-ID: <20121119.190648.56478321385493529.davem@davemloft.net> (raw)
In-Reply-To: <1353082456-21234-2-git-send-email-nicolas.dichtel@6wind.com>
From: Nicolas Dichtel <nicolas.dichtel@6wind.com>
Date: Fri, 16 Nov 2012 17:14:13 +0100
> Now that tunnels can be configured via rtnetlink, this device is not mandatory.
> The default is conservative.
>
> Signed-off-by: Nicolas Dichtel <nicolas.dichtel@6wind.com>
I'm not too thrilled about this change, mostly because of my dislike of
module parameters in general.
But in this case there appears to be real bugs in the two sets of changes
where you add this setup_fb thing.
> @@ -1057,7 +1066,8 @@ static void __net_exit ipip_exit_net(struct net *net)
>
> rtnl_lock();
> ipip_destroy_tunnels(ipn, &list);
> - unregister_netdevice_queue(ipn->fb_tunnel_dev, &list);
> + if (setup_fb)
> + unregister_netdevice_queue(ipn->fb_tunnel_dev, &list);
> unregister_netdevice_many(&list);
> rtnl_unlock();
> }
Users can modify module parameter values via sysfs after the module
is loaded, so you need a more internal and protected state to use
to decide whether you really need to unregister the thing or not.
But to me it's just symptomatic of what a bad idea this is in the
first place.
next prev parent reply other threads:[~2012-11-20 0:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-16 16:14 [PATCH net-next 0/4] Allow to deactivate fb tunnels device Nicolas Dichtel
2012-11-16 16:14 ` [PATCH net-next 1/4] ipip: allow to deactivate the creation of fb dev Nicolas Dichtel
2012-11-16 16:29 ` Stephen Hemminger
2012-11-16 16:46 ` Nicolas Dichtel
2012-11-20 0:07 ` David Miller
2012-11-20 8:30 ` Nicolas Dichtel
2012-11-20 8:34 ` David Miller
2012-11-20 8:41 ` [RESEND PATCH net-next 1/1] sit: allow to configure 6rd tunnels via netlink Nicolas Dichtel
2012-11-20 17:01 ` Stephen Hemminger
2012-11-20 17:11 ` Nicolas Dichtel
2012-11-20 17:17 ` Stephen Hemminger
2012-11-20 17:22 ` Nicolas Dichtel
2012-11-20 18:45 ` David Miller
2012-11-20 0:06 ` David Miller [this message]
2012-11-16 16:14 ` [PATCH net-next 2/4] " Nicolas Dichtel
2012-11-16 16:14 ` [PATCH net-next 3/4] sit: allow to deactivate the creation of fb device Nicolas Dichtel
2012-11-16 16:14 ` [PATCH net-next 4/4] ip6tnl: allow to deactivate the creation of fb dev Nicolas Dichtel
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=20121119.190648.56478321385493529.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.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;
as well as URLs for NNTP newsgroup(s).