From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: linux-modules@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, peterz@infradead.org
Subject: Re: [ARM64][GCC10] Kernel can't load any module due to RWX check
Date: Sat, 29 Aug 2020 15:57:06 +0800 [thread overview]
Message-ID: <5390e084-1b0f-9508-204c-6fae39a7ae96@gmx.com> (raw)
In-Reply-To: <2d00ffc3-1176-1b80-20a5-e7f6babf924a@gmx.com>
[-- Attachment #1.1: Type: text/plain, Size: 1905 bytes --]
On 2020/8/29 下午3:49, Qu Wenruo wrote:
>
>
> On 2020/8/29 下午3:44, Qu Wenruo wrote:
>> Hi,
>>
>> Recently built a v5.9-rc2 kernel, it boots fine, but unable to load any
>> kernel module.
>>
>> After some debugging, it shows that it's due to RWX check failure:
>>
>> load_module: start
>> module_enforce_rwx_sections: index=22 sh_flags=0x7 shf_wx=0x5
>> layout_and_allocate: module enforce rwx sections
>> load_module: failed to alloc layout and allocate
>> load_module: end
>>
>> Futhermore, it's unable to disable the RWX check through "make
>> menuconfig", since the ARCH_OPTIONAL_KERNEL_RWX is no for arm64.
>>
>> The offending section 22 looks like this: (the kernel reports 38
>> sectors, while we only have 37, thus near-by sections are also shown here).
>>
>> 20 .data 00000aa0 0000000000000000 0000000000000000 00086d08
>> 2**3
>> CONTENTS, ALLOC, LOAD, RELOC, DATA
>> 21 __bug_table 000000cc 0000000000000000 0000000000000000 000877a8
>> 2**2
>> CONTENTS, ALLOC, LOAD, RELOC, DATA
>> 22 __dyndbg 0000b9b8 0000000000000000 0000000000000000 00087878
>> 2**3
>> CONTENTS, ALLOC, LOAD, RELOC, DATA
>> 23 .data.unlikely 00000012 0000000000000000 0000000000000000
>> 00093230 2**0
>> CONTENTS, ALLOC, LOAD, DATA
>>
>> I'm using GCC 10.2.0, could this be the cause?
>
> I should check the git log, the module_enforce_rwx_sections() is just
> recently added by commit 5c3a7db0c7ec ("module: Harden STRICT_MODULE_RWX").
>
> Hi Peter, any idea how could this commit causing a regression on arm64
> but not on x86_64?
And obviously, reverting it solves the problem of mine.
(Now happy working 4K sector size btrfs support on 64K page size system)
Thanks,
Qu
>
> Thanks,
> Qu
>
>>
>> Thanks,
>> Qu
>>
>>
>>
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-08-29 7:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-29 7:44 [ARM64][GCC10] Kernel can't load any module due to RWX check Qu Wenruo
2020-08-29 7:49 ` Qu Wenruo
2020-08-29 7:57 ` Qu Wenruo [this message]
2020-08-29 10:03 ` peterz
2020-09-01 12:53 ` Will Deacon
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=5390e084-1b0f-9508-204c-6fae39a7ae96@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-modules@vger.kernel.org \
--cc=peterz@infradead.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;
as well as URLs for NNTP newsgroup(s).