From: "Paul Rolland" <rol@witbe.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, rol@witbe.net
Subject: Re: Linux 2.6.29-rc1
Date: Sun, 11 Jan 2009 11:18:25 +0100 [thread overview]
Message-ID: <20090111111825.49eaee0d@tux.DEF.witbe.net> (raw)
In-Reply-To: <alpine.LFD.2.00.0901101551420.6528@localhost.localdomain>
Hello,
On Sat, 10 Jan 2009 16:13:02 -0800 (PST)
Linus Torvalds <torvalds@linux-foundation.org> wrote:
>
> The merge window is over, and while it is quite possible that I missed a
> few merge requests in the crazy week that is behind us, apart from those
> we should now have most of the bulk of 2.6.29 merged up. And now it's
> just a small matter of making sure it's all stable and ready to go.
>
Don't know if this is important or not, but I have :
WARNING: net/dccp/dccp.o(.text+0xf6): 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+0x53): 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.
Regards,
Paul
--
Paul Rolland E-Mail : rol(at)witbe.net
CTO - Witbe.net SA Tel. +33 (0)1 47 67 77 77
Les Collines de l'Arche Fax. +33 (0)1 47 67 77 99
F-92057 Paris La Defense RIPE : PR12-RIPE
Please no HTML, I'm not a browser - Pas d'HTML, je ne suis pas un
navigateur "Some people dream of success... while others wake up and work
hard at it"
"And they told us, what they wanted...
Was a sound that could kill some-one, from a distance." -- Kate Bush
next prev parent reply other threads:[~2009-01-11 10:18 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-11 0:13 Linux 2.6.29-rc1 Linus Torvalds
2009-01-11 8:04 ` Willy Tarreau
2009-01-11 10:18 ` Paul Rolland [this message]
2009-01-11 12:07 ` David Miller
2009-01-11 12:23 ` Petr Titera
2009-01-11 13:23 ` Jaswinder Singh Rajput
2009-01-11 13:54 ` Ingo Molnar
2009-01-11 14:56 ` Petr Titera
2009-01-11 17:29 ` Gene Heskett
2009-01-11 17:55 ` Paul Rolland
2009-01-11 18:03 ` Ingo Molnar
2009-01-11 19:46 ` Paul Rolland
2009-01-11 20:10 ` Linux 2.6.29-rc1 MAJOR advisory Gene Heskett
2009-01-11 21:06 ` Torsten Kaiser
2009-01-12 2:50 ` Gene Heskett
2009-01-12 6:57 ` Torsten Kaiser
2009-01-12 7:15 ` Justin P. Mattock
2009-01-11 21:28 ` Linux 2.6.29-rc1 Maciej Rutecki
2009-01-11 21:35 ` Jesper Juhl
2009-01-11 21:38 ` Maciej Rutecki
2009-01-12 22:05 ` Simon Holm Thøgersen
-- strict thread matches above, loose matches on Subject: below --
2009-01-11 16:40 Torsten Schmidt
2009-01-11 18:19 ` Ingo Molnar
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=20090111111825.49eaee0d@tux.DEF.witbe.net \
--to=rol@witbe.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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