linux-kernel - Re: [2.6 patch] remove the broken SCSI

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: <1166198454.2846.10.camel@mulgrave.il.steeleye.com>
Date:	Fri, 15 Dec 2006 10:00:54 -0600
From:	James Bottomley <James.Bottomley@...elEye.com>
To:	Krzysztof Halasa <khc@...waw.pl>
Cc:	Adrian Bunk <bunk@...sta.de>, Andrew Morton <akpm@...l.org>,
	linux-scsi@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [2.6 patch] remove the broken SCSI_SEAGATE driver

On Fri, 2006-12-15 at 14:34 +0100, Krzysztof Halasa wrote:
> Adrian Bunk <bunk@...sta.de> writes:
> 
> > There must have been a compile error that has since been fixed, but I 
> > don't remember the details of this specific driver and I don't have 
> > such old compile logs anymore.
> 
> I wonder if we could gather some usage statistics, especially WRT
> really old hardware.
> 
> Perhaps we could invent some MODULE_WARN_OBSOLETE thing which would
> warn users about their drivers being removed in +6m (or maybe +12m),
> unless they let us know at http://qwe or mailto:ads?
> 
> I find it really hard to believe there are still users of things like
> CDU-31A CDs, XT MFM disk controllers, or NCR5380 SCSI host adapters
> (especially the real ones, not DOMEX etc. clones bundled with scanner
> just ~ 10 years ago).

I really don't see a need to declare drivers obsolete unless they bitrot
to the point they're demonstrably useless and no-one wants to step up to
fix them, which is what the BROKEN flag is for.

James


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/