From: Grant Grundler <iod00d@hp.com>
To: Greg KH <greg@kroah.com>
Cc: Jesse Barnes <jbarnes@sgi.com>,
linux-pci@atrey.karlin.mff.cuni.cz, linux-kernel@vger.kernel.org,
linux-ia64@vger.kernel.org, jeremy@sgi.com
Subject: Re: [PATCH] readX_relaxed interface
Date: Thu, 15 Jan 2004 21:50:31 -0800 [thread overview]
Message-ID: <20040116055031.GD13222@cup.hp.com> (raw)
In-Reply-To: <20040116003224.GF23253@kroah.com>
On Thu, Jan 15, 2004 at 04:32:25PM -0800, Greg KH wrote:
[ deleted reminder for readb() to return success/fail codes ]
> Just wanted to put this idea in people's heads that we need to start
> planning for something like it.
I just remembered another part of linux 2.4/2.6 that needs revisiting:
DMA mapping routines don't return an error code.
ie pci_map_single() must panic since it can't return a failure.
It was designed that way on purpose to make life easier for driver
writers (and I agree, it has).
(my guess is x86-64 needs this change more urgently than any other arch.)
I'm sure there are other robustness issues too.
Looking for "panic" will probably give alot of them away.
The current 2.6.1 tree has over 1000 panic() calls.
I used "find -name \*.c | fgrep panic\( | wc ".
And for my amusement:
grundler <506>find drivers/scsi -name \*.c | xargs fgrep panic\( | wc
183 1243 14722
grundler <507>find drivers/net -name \*.c | xargs fgrep panic\( | wc
10 53 662
My point is a substantial number of things can be done to improve
robustness besides (or in addition to?) recovering from IO subsystem
crashes.
grant
prev parent reply other threads:[~2004-01-16 5:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-15 20:49 [PATCH] readX_relaxed interface Jesse Barnes
2004-01-15 22:16 ` Grant Grundler
2004-01-15 22:56 ` Jesse Barnes
2004-01-16 3:19 ` Jeremy Higdon
2004-01-16 0:32 ` Greg KH
2004-01-16 2:21 ` Jesse Barnes
2004-01-16 5:00 ` Linus Torvalds
2004-01-16 17:21 ` Jesse Barnes
2004-01-16 5:00 ` Grant Grundler
2004-01-19 9:31 ` Hironobu Ishii
2004-01-19 18:18 ` Grant Grundler
2004-01-16 5:50 ` Grant Grundler [this message]
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=20040116055031.GD13222@cup.hp.com \
--to=iod00d@hp.com \
--cc=greg@kroah.com \
--cc=jbarnes@sgi.com \
--cc=jeremy@sgi.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
/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