linux-kernel - Re: Areca arcmsr kernel integration for 2.6.18?

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: <1156401274.4256.53.camel@thud.gurulabs.com>
Date:	Thu, 24 Aug 2006 00:34:34 -0600
From:	Dax Kelson <dax@...ulabs.com>
To:	James Bottomley <James.Bottomley@...elEye.com>
Cc:	Greg KH <gregkh@...e.de>, Andrew Morton <akpm@...l.org>,
	Theodore Bullock <tbullock@...tel.com>, robm@...tmail.fm,
	brong@...tmail.fm, erich@...ca.com.tw, greg@...ah.com,
	linux-kernel@...r.kernel.org, Linus Torvalds <torvalds@...l.org>
Subject: Re: Areca arcmsr kernel integration for 2.6.18?

On Wed, 2006-08-23 at 23:11 -0500, James Bottomley wrote:
> On Wed, 2006-08-23 at 17:25 -0600, Dax Kelson wrote:
> > It would be great if the arcmsr driver could be included in 2.6.18 so it
> > can make into all the new distro releases that will be happening the
> > last 3-4 months of the year.
> > 
> > It is completely self contained and it isn't changing any existing code
> > (ergo it can't break anything) so I believe there is quite a bit of
> > precedence for "late" inclusion in 2.6.18?

> There's precedent for putting relatively uncontroversial drivers into
> the -rc tree.  

Indeed, this precedent goes back many years.

> However, arcmsr has had a rather difficult path into the
> kernel.  Moving it into scsi-misc is a signal that it goes from being
> out of tree to in-tree candidate (i.e. I'm happy with the quality now,
> but I'll give other people a chance to voice concerns), but on a slow
> path that allows people time to find problems and fix them.  This path
> also dictates a time line for any final objections arising (i.e. up
> until 2.6.18 is declared).

People have been using the driver out of tree (with all the pain that
out of tree drivers entail) for almost 2 years with few if any problems.
The driver worked OK even before it got whipped into submission shape.

Another data point supporting the stability and well tested nature of
the driver is that a widely used distro has been shipping it since June,
Ubuntu 6.06 LTS.

Like Greg's OLS keynote aptly covered, the Linux hardware model is
geared towards and encourages in-tree drivers. 

In fact, from the keynote "... We have a whole sub-architecture that
only has 2 users in the world out there. We have drivers that I know
have only one user, as there was only one piece of hardware ever made
for it. It just isn't true, we will take drivers for anything into our
tree, as we really want it."

Areca hardware owners have been experiencing the out-of-tree pain for a
long time. James is happy with the quality, it is a new driver, well
tested, has been shipped by a major distro. People have had the ample
chance to voice concerns.

Why prolong the pain? Hook a brother up already.

Dax Kelson

-
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/