linux-kernel - Re: Relocation (type 4) overflow on alpha for big module

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]

Date:   Sun, 14 Oct 2018 18:14:20 -0500
From:   Bob Tracy <rct@...rkin.frus.com>
To:     Michael Cree <mcree@...on.net.nz>, Meelis Roos <mroos@...ux.ee>,
        linux-alpha@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: Relocation (type 4) overflow on alpha for big module

On Mon, Oct 15, 2018 at 07:41:48AM +1300, Michael Cree wrote:
> On Sun, Oct 14, 2018 at 12:33:06PM -0500, Bob Tracy wrote:
> > On Sun, Oct 14, 2018 at 10:07:13AM +0300, Meelis Roos wrote:
> > > I decided to try btrfs on one of my alphas and got a surprise - btrfs module does not load:
> > 
> > Confirmed on a PWS 433au running 4.19.0-rc6 with latest "sid" toolchain.
> 
> Known and long-standing problem in the Alpha kernel module loader.
> Requires extra code implmented to support loading such large modules
> which no one has done.  Workaround is to build the kernel with such
> modules (e.g. radeon, btrfs) in-built.

ACK on the workaround.  Never noticed the problem with, per your
example, the radeon driver because I seldom build a driver as a
module for a piece of hardware (or filesystem type) that's present
at boot and won't be removed.

--Bob