module: LLVMLinux: Fix section mismatch issues on alias usage
PATCH 1/1 module: LLVMLinux: Fix section mismatch issues on alias usage
From: Jan-Simon Möller <[email protected]>
Attribute aliases don't inherit the link section name when compiled with clang. As a result, the linking section needs to be explicitly specified when building a module. This behavior is undefined in the standard which is why it differs from compiler to compiler.
Author: PaX Team <[email protected]> ML-Post: http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20120507/142707.html URL: http://llvm.linuxfoundation.org Merge: Jan-Simon Möller <[email protected]>
--- include/linux/init.h | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-)
include/linux/init.h +3 -2
@@ -297,13 +297,14 @@ void __init parse_early_options(char *cmdline);#define module_init (initfn) \ static inline initcall_t __inittest(void) \ { return initfn; } \ - int init_module(void) __attribute__((alias(#initfn))); + int init_module(void) __section(.init) __attribute__((alias(#initfn)));/* This is only required if you want to be unloadable. */ #define module_exit (exitfn) \ static inline exitcall_t __exittest(void) \ { return exitfn; } \ - void cleanup_module(void) __attribute__((alias(#exitfn))); + void cleanup_module(void) __section(.exit) \ + __attribute__((alias(#exitfn)));#define __setup_param (str, unique_id, fn)/* nothing */ #define __setup (str, func)/* nothing */
Signature · 1 line
1.8.3.2
Quoted 1 line · On 14-02-20 11:28 PM, [email protected] wrote:
From: Jan-Simon Möller <[email protected]>
^^^^^^^^^^^^^^
This line implies that Jan is the author.
Quoted 5 lines
Attribute aliases don't inherit the link section name when compiled with clang. As a result, the linking section needs to be explicitly specified when building a module. This behavior is undefined in the standard which is why it differs from compiler to compiler.
But is there a good reason why clang doesn't inherit them in the interest of compatibility with gcc and existing code?
Quoted 5 lines
Author: PaX Team <[email protected]> ML-Post: http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20120507/142707.html URL: http://llvm.linuxfoundation.org Merge: Jan-Simon Möller <[email protected]>
I know we've seen the faceless entity "PaX Team" before, but can we please not make it worse by adding a bunch of other non standard tag line formats? And ideally have a real human name for the author too.
Paul.
--
Quoted 28 lines
Signed-off-by Jan-Simon Möller <[email protected]>Signed-off-by Behan Webster <[email protected]>--- include/linux/init.h | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-)include/linux/init.h +3
-2@@ -297,13 +297,14 @@ void __init parse_early_options(char *cmdline);#define module_init (initfn) \ static inline initcall_t __inittest(void) \ { return initfn; } \ - int init_module(void) __attribute__((alias(#initfn))); + int init_module(void) __section(.init) __attribute__((alias(#initfn)));/* This is only required if you want to be unloadable. */ #define module_exit (exitfn) \ static inline exitcall_t __exittest(void) \ { return exitfn; } \ - void cleanup_module(void) __attribute__((alias(#exitfn))); + void cleanup_module(void) __section(.exit) \ + __attribute__((alias(#exitfn)));#define __setup_param (str, unique_id, fn)/* nothing */ #define __setup (str, func)/* nothing */
Quoted 6 lines · Paul Gortmaker
Quoted 4 lines
Attribute aliases don't inherit the link section name when compiled with clang. As a result, the linking section needs to be explicitly specified when building a module. This behavior is undefined in the standard which is why it differs from compiler to compiler.
But is there a good reason why clang doesn't inherit them in the interest of compatibility with gcc and existing code?
There is no reason other than it doesn't appear to be documented behaviour anywhere that can be found. It seems like this use of an aliased symbol inheriting attributes never came up before. Personally I think the kernel code pushes compilers harder than most other code bases. :)
Having said that, it seems since we first started needing this patch to build the kernel with clang, this issue may have been fixed in the most recent updates to clang in the last few weeks. I've been testing with the latest released version of clang v3.4 (since clang recently when through a merge window of their own) which still requires this patch. However in appears that this issue may now have been fixed in mainline clang. I'll do some more testing to verify and get back to this thread.
Quoted 1 line
I know we've seen the faceless entity "PaX Team" before, but can we please not make it worse by adding a bunch of other non standard tag line formats? And ideally have a real human name for the author too.
Fair enough. Will fix and resubmit if the patch proves to still be necessary.
Thanks for the input,
Behan
Signature · 2 lines
Behan Webster [email protected]