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]
Message-ID: <CAHk-=whFLZ67ffzt1juryCYcYz6eL_XjQF8WucDzwUR5H65+rA@mail.gmail.com>
Date:   Thu, 2 Nov 2023 07:28:45 -1000
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Frank Scheiner <frank.scheiner@....de>
Cc:     Arnd Bergmann <arnd@...db.de>,
        Tomáš Glozar <tglozar@...il.com>,
        linux-ia64@...r.kernel.org, linux-kernel@...r.kernel.org,
        Linux-Arch <linux-arch@...r.kernel.org>,
        Ard Biesheuvel <ardb@...nel.org>
Subject: Re: [GIT PULL] asm-generic updates for v6.7

On Thu, 2 Nov 2023 at 00:24, Frank Scheiner <frank.scheiner@....de> wrote:
>
> so the ia64 removal happened despite the efforts - not only from us - to
> keep it alive in Linux. That is a - sad - fact now.

Well, I'd have personally been willing to resurrect it, but I was told
several times that other projects were basically just waiting for the
kernel support to die.

Has the itanium situation really changed?

The thing is, nobody doing new kernel code wants to deal with itanium,
so relegating it to the same situation that i386 support was ("it
still works in old kernels") doesn't seem to be a huge issue for the
people who actually want to use those machines.

That said, I'd be willing to resurrect itanium support, even though I
personally despise the architecture with a passion for being
fundamentally based on faulty design premises, and an implementation
based on politics rather than good technical design.

But only if it turns out to actually have some long-term active
interest (ie I'd compare it to the situation with m68k etc - clearly
dead architectures that we still support despite them being not
relevant - because some people care and they don't cause pain).

So I'd be willing to come back to the "can we resurrect it"
discussion, but not immediately - more along the lines of a "look,
we've been maintaining it out of tree for a year, the other
infrastructure is still alive, there is no impact on the rest of the
kernel, can we please try again"?

               Linus

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ