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]

Date:	Sun, 17 Dec 2006 14:22:46 -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 Sun, 2006-12-17 at 21:03 +0100, Krzysztof Halasa wrote:
> James Bottomley <James.Bottomley@...elEye.com> writes:
> 
> > 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.
> 
> How do you know if the driver is broken? Especially if it still
> compiles?
> 
> Some of these things are 20 years old.

One of the touted benefits of Linux is that we run on old hardware.
Unless the driver is demonstrably wrong (and they do become so as the
APIs evolve) or it fails to compile because of bitrotting, there's no
real urgency to remove it, is there?

The reverse (how do you know if someone's still using the driver) is
equally hard to determine.

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/