From: Arnaldo Carvalho de Melo <acme@redhat.com>
To: Leonardo Potenza <lpotenza@inwind.it>,
David Miller <davem@davemloft.net>,
Gerrit Renker <gerrit@erg.abdn.ac.uk>
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
DCCP Mailing List <dccp@vger.kernel.org>,
Linux Networking Development Mailing List
<netdev@vger.kernel.org>
Subject: Re: [PATCH] net: fix section mismatch warnings in dccp/ccids/lib/tfrc.c
Date: Thu, 8 Jan 2009 21:28:47 -0200 [thread overview]
Message-ID: <20090108232847.GV23891@ghostprotocols.net> (raw)
In-Reply-To: <200901081957.03413.lpotenza@inwind.it>
Adding netdev to the CC list.
Em Thu, Jan 08, 2009 at 07:57:03PM +0100, Leonardo Potenza escreveu:
> From: Leonardo Potenza <lpotenza@inwind.it>
>
> Removed the __exit annotation of tfrc_lib_exit(), in order to suppress the following section mismatch messages:
>
> WARNING: net/dccp/dccp.o(.text+0xd9): Section mismatch in reference from the function ccid_cleanup_builtins() to the function .exit.text:tfrc_lib_exit()
> The function ccid_cleanup_builtins() references a function in an exit section.
> Often the function tfrc_lib_exit() has valid usage outside the exit section
> and the fix is to remove the __exit annotation of tfrc_lib_exit.
>
> WARNING: net/dccp/dccp.o(.init.text+0x48): Section mismatch in reference from the function ccid_initialize_builtins() to the function .exit.text:tfrc_lib_exit()
> The function __init ccid_initialize_builtins() references
> a function __exit tfrc_lib_exit().
> This is often seen when error handling in the init function
> uses functionality in the exit path.
> The fix is often to remove the __exit annotation of
> tfrc_lib_exit() so it may be used outside an exit section.
>
> Signed-off-by: Leonardo Potenza <lpotenza@inwind.it>
> ---
> Index: linux-2.6/net/dccp/ccids/lib/tfrc.c
> ===================================================================
> --- linux-2.6.orig/net/dccp/ccids/lib/tfrc.c 2009-01-08 19:19:50.000000000 +0100
> +++ linux-2.6/net/dccp/ccids/lib/tfrc.c 2009-01-08 19:20:07.000000000 +0100
> @@ -36,7 +36,7 @@ out:
> return rc;
> }
>
> -void __exit tfrc_lib_exit(void)
> +void tfrc_lib_exit(void)
> {
> tfrc_rx_packet_history_exit();
> tfrc_tx_packet_history_exit();
Thanks Leonardo,
Dave/Gerrit,
Please apply.
Acked-by: Arnaldo Carvalho de Melo <acme@redhat.com>
Thanks,
- Arnaldo
next parent reply other threads:[~2009-01-08 23:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200901081957.03413.lpotenza@inwind.it>
2009-01-08 23:28 ` Arnaldo Carvalho de Melo [this message]
2009-01-08 23:43 ` [PATCH] net: fix section mismatch warnings in dccp/ccids/lib/tfrc.c David Miller
2009-01-10 17:24 ` gerrit
2009-01-11 8:11 ` 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=20090108232847.GV23891@ghostprotocols.net \
--to=acme@redhat.com \
--cc=davem@davemloft.net \
--cc=dccp@vger.kernel.org \
--cc=gerrit@erg.abdn.ac.uk \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lpotenza@inwind.it \
--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;
as well as URLs for NNTP newsgroup(s).