summaryrefslogtreecommitdiff
path: root/net/bridge/br_sysfs_br.c
diff options
context:
space:
mode:
authorJeff Mahoney <jeffm@suse.com>2010-02-24 13:59:23 -0500
committerSteven Rostedt <rostedt@goodmis.org>2010-02-25 09:38:11 -0500
commit86c38a31aa7f2dd6e74a262710bf8ebf7455acc5 (patch)
tree167d2c46917233373e597cc5f82d3f9132170e65 /net/bridge/br_sysfs_br.c
parent0c54dd341fb701928b8e5dca91ced1870c55b05b (diff)
tracing: Fix ftrace_event_call alignment for use with gcc 4.5
GCC 4.5 introduces behavior that forces the alignment of structures to use the largest possible value. The default value is 32 bytes, so if some structures are defined with a 4-byte alignment and others aren't declared with an alignment constraint at all - it will align at 32-bytes. For things like the ftrace events, this results in a non-standard array. When initializing the ftrace subsystem, we traverse the _ftrace_events section and call the initialization callback for each event. When the structures are misaligned, we could be treating another part of the structure (or the zeroed out space between them) as a function pointer. This patch forces the alignment for all the ftrace_event_call structures to 4 bytes. Without this patch, the kernel fails to boot very early when built with gcc 4.5. It's trivial to check the alignment of the members of the array, so it might be worthwhile to add something to the build system to do that automatically. Unfortunately, that only covers this case. I've asked one of the gcc developers about adding a warning when this condition is seen. Cc: stable@kernel.org Signed-off-by: Jeff Mahoney <jeffm@suse.com> LKML-Reference: <4B85770B.6010901@suse.com> Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
Diffstat (limited to 'net/bridge/br_sysfs_br.c')
0 files changed, 0 insertions, 0 deletions