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] [thread-next>] [day] [month] [year] [list]
Date:   Mon, 22 Aug 2022 16:19:49 +0800
From:   Qu Wenruo <quwenruo.btrfs@....com>
To:     Willy Tarreau <w@....eu>
Cc:     Greg KH <gregkh@...uxfoundation.org>,
        stable <stable@...r.kernel.org>,
        "linux-btrfs@...r.kernel.org" <linux-btrfs@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        linux-x86_64@...r.kernel.org
Subject: Re: LTS kernel Linux 4.14.290 unable to boot with edk2-ovmf (x86_64
 UEFI runtime)



On 2022/8/22 16:04, Willy Tarreau wrote:
> On Mon, Aug 22, 2022 at 03:49:51PM +0800, Qu Wenruo wrote:
>> Yeah, I'm pretty sure my toolchain is too new for v4.14.0. But my distro
>> only provides the latest and mostly upstream packages.
>
> Then there's something odd in your use case. Old kernels are aimed at
> those who need to have systems on which nothing changes. It's particularly
> strange to be stuck in the past for the kernel but to continually upgrade
> userland. Most often it's the opposite that's seen.

Yep, that's my bad, just too lazy to get a time-period correct distro,
or learn other package management tools from other distros.

>
> Regardless, if you need an older compiler, just use these ones:
>
>     https://mirrors.edge.kernel.org/pub/tools/crosstool/
>
> They go back to 4.9.4 for x86, you'll surely find the right one for your
> usage. I've long used 4.7.4 for kernels up to 4.9 and 6.5 for 4.19 and
> above, so something within that area will surely match your needs.

BTW, it would be way more awesome if the page can provide some hint on
the initial release date of the compilers.

It would help a lot of choose the toolchain then.

>
>> It may be a even worse disaster to find a way to rollback to older
>> toolchains using my distro...
>
> No, using a prebuilt toolchain like those above is quite trivial and
> it will avoid messing up with your local packages. That's the best
> solution I can recommend.

Thanks for all the info, it really helps a lot,
Qu

>
> Willy

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ