From: David Miller <davem@davemloft.net>
To: JBeulich@suse.com
Cc: netdev@vger.kernel.org, netfilter-devel@vger.kernel.org,
sam@ravnborg.org, xemul@openvz.org, ebiederm@xmission.com
Subject: Re: [PATCH] adjust __net_exit
Date: Fri, 16 Mar 2012 22:18:13 -0700 (PDT) [thread overview]
Message-ID: <20120316.221813.236130733754848615.davem@davemloft.net> (raw)
In-Reply-To: <4F588BEC020000780007710A@nat28.tlf.novell.com>
From: "Jan Beulich" <JBeulich@suse.com>
Date: Thu, 08 Mar 2012 09:37:32 +0000
> __net_exit, judging by the majority of its uses, was intended to serve
> as an abstraction to allow calling such annotated functions from both
> __init and __exit functions. Using the (bogus and unused elsewhere)
> __exit_refok to implement this is inefficient - any non-modular code
> really can reside in __init (as non-modular __exit code is never used).
>
> Therefore, adjust __net_exit to resolve to nothing (i.e. normal .text)
> in modules, and __init in the core kernel.
>
> A few other adjustments are necessary/possible with this done - those
> were likely just oversights when added originally.
>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
[ I have been waiting for more than a week for a netns developer
to review this patch, I guess I'm too optimistic these days. :-( ]
The only reason you think __exit_refok is "bogus" is because it's
semantics got changed by Sam Ravnborg in commit
312b1485fb509c9bc32eda28ad29537896658cb8 ("Introduce new section
reference annotations tags: __ref, __refdata, __refconst")
Beforehand the __exit_refok was a real .exit section, so it got
completely discarded AT LINK TIME. Now it sits together with
__init_refok which is an unremovable kernel image section, which
neither gets removed at compile time nor boot time.
So __exit_refok did exactly what you say it should do before Sam's
change.
It's just completely stupid to change the netns section defines,
and instead we should revert __exit_refok to mean what it always
meant previously.
I'm not applying this patch.
next prev parent reply other threads:[~2012-03-17 5:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-08 9:37 [PATCH] adjust __net_exit Jan Beulich
2012-03-17 5:18 ` David Miller [this message]
2012-03-17 23:03 ` Sam Ravnborg
2012-03-19 0:41 ` Eric W. Biederman
2012-03-19 8:14 ` Jan Beulich
2012-03-19 8:47 ` Sam Ravnborg
2012-03-19 9:09 ` Jan Beulich
2012-03-20 2:17 ` Eric W. Biederman
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=20120316.221813.236130733754848615.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=JBeulich@suse.com \
--cc=ebiederm@xmission.com \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=xemul@openvz.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;
as well as URLs for NNTP newsgroup(s).