mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andre Hedrick <andre@linux-ide.org>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
	"Gustafson, Geoffrey R" <geoffrey.r.gustafson@intel.com>,
	"'Andy Pfiffer'" <andyp@osdl.org>,
	cgl_discussion@osdl.org, "Rhoads, Rob" <rob.rhoads@intel.com>,
	hardeneddrivers-discuss@lists.sourceforge.net,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Hardeneddrivers-discuss] RE: [cgl_discussion] Some Initial Comments on DDH-Spec-0.5h.pdf
Date: Tue, 24 Sep 2002 20:54:38 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.10.10209242018450.6896-100000@master.linux-ide.org> (raw)
In-Reply-To: <3D900DBA.6080400@pobox.com>

On Tue, 24 Sep 2002, Jeff Garzik wrote:

> Eric W. Biederman wrote:
> > Oh, and don't forget that the hardware specification that drivers are
> > written to, many times are not generally available greatly reducing 
> > the pool of capable people who have the opportunity to review the and
> > debug the drivers.  I would make it a requirement for a hardened
> > driver that both the code and the hardware documentation be publicly
> > available so the code can easily be reviewed by as many people as wish
> > to.
> 
> 
> This is a good point that bears highlighting.  Donald Becker's [and thus 
> the kernel's] eepro100.c had certain bugs for years, simply because 
> access to Intel E100 hardware docs was damn near impossible to obtain.

Jeff, 

You know that every hardware vendor will clam it works well under
MicroSoft, so why does it fail under Linux.  This is the classic one-liner
we all have gotten.  The reality is closed software is used to hide all
the flaws and failures of made by the ASIC people.  I would love to shove
the brain dead asic designer of the original PIIX4 AB/EB off a cliff on
fire for being absolutely "stupid".  Sorry this is as nice an clean as I
can say this and not dust off the flame thrower.

> I don't see driver hardening being very feasible on such drivers, where 
> the vendor refuses to allow kernel engineers access needed to get their 
> hardware working and stable.  [why vendors want crappy Linux support, 
> I'll never know]

Worse is getting a spec that says, "no work around".
When the reality is the OEM hardware vendor will not take ownership of 
their errors and disclose a good proper work-around.

Cheers,

Andre Hedrick
LAD Storage Consulting Group


  reply	other threads:[~2002-09-25  3:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <EDC461A30AC4D511ADE10002A5072CAD01FD8CEA@orsmsx119.jf.intel.com>
2002-09-24  1:41 ` Jeff Garzik
2002-09-24  6:33   ` Eric W. Biederman
2002-09-24  7:01     ` Jeff Garzik
2002-09-25  3:54       ` Andre Hedrick [this message]
2002-09-25  7:12         ` Eric W. Biederman
2002-09-30  6:40   ` Pavel Machek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.10.10209242018450.6896-100000@master.linux-ide.org \
    --to=andre@linux-ide.org \
    --cc=andyp@osdl.org \
    --cc=cgl_discussion@osdl.org \
    --cc=ebiederm@xmission.com \
    --cc=geoffrey.r.gustafson@intel.com \
    --cc=hardeneddrivers-discuss@lists.sourceforge.net \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rob.rhoads@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®