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: <20230215151547.GA3766362@roeck-us.net>
Date:   Wed, 15 Feb 2023 07:15:47 -0800
From:   Guenter Roeck <linux@...ck-us.net>
To:     Ard Biesheuvel <ardb@...nel.org>
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>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        linux-ia64@...r.kernel.org
Subject: Re: [RFC PATCH] MAINTAINERS: Mark Itanium/IA64 as 'dead'

On Sat, Jan 28, 2023 at 01:29:04PM +0100, Ard Biesheuvel wrote:
> Create a new status 'dead' which conveys that a subsystem is
> unmaintained and scheduled for removal, and developers are free to
> behave as if it's already gone. Also, automated build tests should
> ignore such subsystems, or at least notify only those who are known to
> have an interest in the subsystem in particular.
> 
> Given that Itanium/IA64 has no maintainer, is no longer supported in
> QEMU (for boot testing under emulation) and does not seem to have a user
> base beyond a couple of machines used by distros to churn out packages,
> let's mark it as dead. This shall mean that any treewide changes (such
> as changes to the EFI subsystem, which I maintain) can be made even if
> they might cause build or boot time regressions on IA64 machines. Also,
> mark the port as scheduled for removal after the next LTS release.
> 

Since this just came up, I very much prefer complete removal. I don't
see the point of keeping dead code in the tree. That is still hidden
maintenance effort.

If this proliferates, we'll end up having to parse the MAINTAINERS file
for code marked "Dead" to ensure that we don't accidentally send e-mails
to the wrong people, or we risk getting complaints about sending reports
for such code. That puts extra burden on maintainers of automated test
beds, which I think is not really appropriate. If the code is dead,
remove it, period.

For my part, I'll drop my test bed support immediately after this patch
made it in, following the guidance above.

Guenter

> Cc: Jonathan Corbet <corbet@....net>
> Cc: Arnd Bergmann <arnd@...db.de>
> Cc: Tony Luck <tony.luck@...el.com>
> Cc: Jessica Clarke <jrtc27@...c27.com>
> Cc: John Paul Adrian Glaubitz <glaubitz@...sik.fu-berlin.de>
> Cc: Matthew Wilcox <willy@...radead.org>
> Cc: Marc Zyngier <maz@...nel.org>
> Cc: Guenter Roeck <linux@...ck-us.net>
> Cc: Linus Torvalds <torvalds@...ux-foundation.org>
> Cc: linux-ia64@...r.kernel.org
> Link: https://lore.kernel.org/all/CAMj1kXEqbMEcrKYzz2-huLPMnotPoxFY8adyH=Xb4Ex8o98x-w@mail.gmail.com/
> Signed-off-by: Ard Biesheuvel <ardb@...nel.org>
> ---
>  MAINTAINERS | 10 +++++++++-
>  1 file changed, 9 insertions(+), 1 deletion(-)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 5b74014994f5c1cc..5481967c2112e8ce 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -94,6 +94,14 @@ Descriptions of section entries and preferred order
>  	   Obsolete:	Old code. Something tagged obsolete generally means
>  			it has been replaced by a better system and you
>  			should be using that.
> +	   Dead:	Code has no maintainer and no significant user base,
> +			and is scheduled for removal. Developers are free to
> +			ignore it when it comes to testing bug fixes or other
> +			code changes, and automated build test systems must not
> +			report any detected issues, except possibly to mailing
> +			lists or other recipients that have opted in
> +			specifically to receiving reports about the state of
> +			this code.
>  	W: *Web-page* with status/info
>  	Q: *Patchwork* web based patch tracking system site
>  	B: URI for where to file *bugs*. A web-page with detailed bug
> @@ -9833,7 +9841,7 @@ F:	include/linux/i3c/
>  
>  IA64 (Itanium) PLATFORM
>  L:	linux-ia64@...r.kernel.org
> -S:	Orphan
> +S:	Dead # to be removed after the 2023 LTS release
>  F:	Documentation/ia64/
>  F:	arch/ia64/
>  
> -- 
> 2.39.0
> 

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ