From: Jessica Yu <jeyu@redhat.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
David Daney <david.daney@cavium.com>,
Jason Baron <jbaron@akamai.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Sachin Sant <sachinp@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org, linux-mips@linux-mips.org,
linuxppc-dev@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org,
Chris Metcalf <cmetcalf@mellanox.com>,
Ralf Baechle <ralf@linux-mips.org>,
Russell King <linux@armlinux.org.uk>,
Rabin Vincent <rabin@rab.in>, Paul Mackerras <paulus@samba.org>,
Anton Blanchard <anton@samba.org>, Ingo Molnar <mingo@kernel.org>,
Zhigang Lu <zlu@ezchip.com>
Subject: Re: [PATCH] module: set __jump_table alignment to 8
Date: Thu, 2 Mar 2017 13:26:25 -0500 [thread overview]
Message-ID: <20170302182625.GB13268@packer-debian-8-amd64.digitalocean.com> (raw)
In-Reply-To: <20170302131119.6f52203f@gandalf.local.home>
+++ Steven Rostedt [02/03/17 13:11 -0500]:
>
>Can I get an Ack from a module maintainer?
Acked-by: Jessica Yu <jeyu@redhat.com>
Thanks!
Jessica
>On Wed, 1 Mar 2017 14:04:53 -0800
>David Daney <david.daney@cavium.com> wrote:
>
>> For powerpc the __jump_table section in modules is not aligned, this
>> causes a WARN_ON() splat when loading a module containing a __jump_table.
>>
>> Strict alignment became necessary with commit 3821fd35b58d
>> ("jump_label: Reduce the size of struct static_key"), currently in
>> linux-next, which uses the two least significant bits of pointers to
>> __jump_table elements.
>>
>> 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>
>> Tested-by: Sachin Sant <sachinp@linux.vnet.ibm.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)) }
>> }
>
next prev parent reply other threads:[~2017-03-02 18:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-01 22:04 David Daney
2017-03-02 10:47 ` Michael Ellerman
2017-03-02 11:18 ` Michael Ellerman
2017-03-02 17:44 ` Steven Rostedt
2017-03-03 3:34 ` Michael Ellerman
2017-03-02 15:30 ` Jason Baron
2017-03-02 18:11 ` Steven Rostedt
2017-03-02 18:26 ` Jessica Yu [this message]
2017-03-02 19:24 ` David Daney
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=20170302182625.GB13268@packer-debian-8-amd64.digitalocean.com \
--to=jeyu@redhat.com \
--cc=anton@samba.org \
--cc=cmetcalf@mellanox.com \
--cc=david.daney@cavium.com \
--cc=jbaron@akamai.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux@armlinux.org.uk \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mingo@kernel.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=rabin@rab.in \
--cc=ralf@linux-mips.org \
--cc=rostedt@goodmis.org \
--cc=rusty@rustcorp.com.au \
--cc=sachinp@linux.vnet.ibm.com \
--cc=zlu@ezchip.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®