linux-kernel - Re: [question] insert ko failed because count_plts return 0 when CONFIG_RANDOMIZE

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAMj1kXGbwYqy3FCPuXw9nTtpU7MFduTr99Fo2A5cXe6VRvP1Xg@mail.gmail.com>
Date:   Thu, 25 Mar 2021 08:35:33 +0100
From:   Ard Biesheuvel <ardb@...nel.org>
To:     "chenjun (AM)" <chenjun102@...wei.com>
Cc:     "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "linux-arm-kernel@...ts.infradead.org" 
        <linux-arm-kernel@...ts.infradead.org>,
        Will Deacon <will.deacon@....com>,
        Catalin Marinas <catalin.marinas@....com>,
        "Xiangrui (Euler)" <rui.xiang@...wei.com>,
        liuyanshi <liuyanshi@...wei.com>,
        wuzengkun <wuzengkun@...ilicon.com>
Subject: Re: [question] insert ko failed because count_plts return 0 when
 CONFIG_RANDOMIZE_BASE is not set

On Thu, 25 Mar 2021 at 07:22, chenjun (AM) <chenjun102@...wei.com> wrote:
>
> 在 2021/3/24 16:29, Ard Biesheuvel 写道:
> > On Wed, 24 Mar 2021 at 08:27, chenjun (AM) <chenjun102@...wei.com> wrote:
> >>
> >> Hi
> >>
> >> I make a Image for arm64 (without CONFIG_RANDOMIZE_BASE). And a ko (13M)
> >> can not be inserted.
> >>
> >
> > How many large modules have you loaded already? The module region is
> > only 128 MB, so if your modules are huge, you may run out of space.
> >
> > Please check the kernel VA address and the load address of the module,
> > and check whether they are more than 128 MB apart.
> >
>
> Thanks Ard
>
> I will check it.
>
> One more question, why is CONFIG_ARM64_MODULE_PLTS depended on
> CONFIG_RANDOMIZE_BASE?
>

Because modules should never go out of branching range if the
placement is not randomized and the total size of all modules does not
exceed 128 MB.