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: <CAMj1kXGXCFFQQObtkGje=Hym0GuEgR3h85MX8d1_hBb=b3Fxdg@mail.gmail.com>
Date:   Fri, 12 May 2023 16:45:55 +0200
From:   Ard Biesheuvel <ardb@...nel.org>
To:     Florian Weimer <fw@...eb.enyo.de>
Cc:     linux-kernel@...r.kernel.org, Jonathan Corbet <corbet@....net>,
        Arnd Bergmann <arnd@...db.de>, Tony Luck <tony.luck@...el.com>,
        Jessica Clarke <jrtc27@...c27.com>,
        John Paul Adrian Glaubitz <glaubitz@...sik.fu-berlin.de>,
        Matthew Wilcox <willy@...radead.org>,
        Marc Zyngier <maz@...nel.org>,
        Guenter Roeck <linux@...ck-us.net>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        linux-ia64@...r.kernel.org
Subject: Re: [RFC PATCH 0/5] Retire IA64/Itanium support

On Fri, 17 Mar 2023 at 23:56, Florian Weimer <fw@...eb.enyo.de> wrote:
>
> * Ard Biesheuvel:
>
> > The IA64 port of Linux has no maintainer, and according to a report from
> > its only remaining user [0], it has been broken for a month and nobody
> > cares.
> >
> > Given that keeping a complex but unused architecture alive uses up
> > valuable developer bandwidth, let's just get rid of it.
> >
> > This supersedes my patch proposing to mark it as 'dead', which received
> > no replies from anyone that wants to keep it alive. [1]
>
> Is this still going ahead?
>
> In userspace, ia64 is of course full of special cases, too, so many of
> us really want to see it gone, but we can't really start the removal
> process while there is still kernel support.

I brought this up again [0] in the context of GRUB (which has similar
issues related to EFI the the kernel has) and Adrian suggested to
raise this discussion more widely, perhaps on the distributions
mailing list, among other places.

Do you have any recommendations for a venue where we might find the
right mix of people who can drive this to a conclusion one way or the
other?

Thanks,


[0] https://lists.gnu.org/archive/html/grub-devel/2023-05/msg00068.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ