All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Daney <david.daney@cavium.com>
Subject: [PATCH] module: set __jump_table alignment to 8
Date: Tue, 28 Feb 2017 12:10:02 -0800	[thread overview]
Message-ID: <20170228201002.9IMv8cgyvtKiLdmN4ZlrvcdFs4eL4r2nPuOjKqqee2I@z> (raw)

For powerpc the __jump_table section in modules is not aligned, this
causes an OOPS when loading a module containing a __jump_table.

Fix by forcing __jump_table to 8, which is the same alignment used for
this section in the kernel proper.

Signed-off-by: David Daney <david.daney@cavium.com>
---
 scripts/module-common.lds | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/scripts/module-common.lds b/scripts/module-common.lds
index 73a2c7d..53234e8 100644
--- a/scripts/module-common.lds
+++ b/scripts/module-common.lds
@@ -19,4 +19,6 @@ SECTIONS {
 
 	. = ALIGN(8);
 	.init_array		0 : { *(SORT(.init_array.*)) *(.init_array) }
+
+	__jump_table		0 : ALIGN(8) { KEEP(*(__jump_table)) }
 }
-- 
2.9.3


--------------2F06A5F2FED84D3DFBAD5183--

             reply	other threads:[~2017-02-28 20:10 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-28 20:10 David Daney [this message]
2017-03-01 22:04 [PATCH] module: set __jump_table alignment to 8 David Daney
2017-03-01 22:04 ` David Daney
2017-03-02 10:47 ` Michael Ellerman
2017-03-02 10:47   ` Michael Ellerman
2017-03-02 10:47   ` Michael Ellerman
2017-03-02 11:18   ` Michael Ellerman
2017-03-02 11:18     ` Michael Ellerman
2017-03-02 11:18     ` Michael Ellerman
2017-03-02 17:44     ` Steven Rostedt
2017-03-02 17:44       ` Steven Rostedt
2017-03-03  3:34       ` Michael Ellerman
2017-03-03  3:34         ` Michael Ellerman
2017-03-02 15:30 ` Jason Baron
2017-03-02 15:30   ` Jason Baron
2017-03-02 18:11 ` Steven Rostedt
2017-03-02 18:11   ` Steven Rostedt
2017-03-02 18:26   ` Jessica Yu
2017-03-02 18:26     ` Jessica Yu
2017-03-02 19:24     ` David Daney
2017-03-02 19:24       ` David Daney
2017-03-02 22:49       ` Jessica Yu
2017-03-02 22:49         ` Jessica Yu

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=20170228201002.9IMv8cgyvtKiLdmN4ZlrvcdFs4eL4r2nPuOjKqqee2I@z \
    --to=david.daney@cavium.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.