From: David Miller <davem@davemloft.net>
To: James.Bottomley@HansenPartnership.com
Cc: akpm@linux-foundation.org, torvalds@linux-foundation.org,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PATCH] firs round of SCSI bug fixes for 2.6.29-rc1
Date: Fri, 16 Jan 2009 11:09:31 -0800 (PST) [thread overview]
Message-ID: <20090116.110931.166270342.davem@davemloft.net> (raw)
In-Reply-To: <1232131733.3224.46.camel@localhost.localdomain>
From: James Bottomley <James.Bottomley@HansenPartnership.com>
Date: Fri, 16 Jan 2009 13:48:53 -0500
> On Fri, 2009-01-16 at 09:09 -0800, Andrew Morton wrote:
> > Doing a panic() after we've already detected an error is plain nasty.
> > Is there no way in which we can allow the kernel to continue?
>
> There's a long thread discussing this very point on linux-scsi. The
> short version is "no, it's only used for debugging firmware and if
> you've corrupted your firmware to this point you need the machine
> halting".
Long thread or not, taking out one's entire system because one
device hits a fail state is always wrong.
If I have other block devices which are working, all I want
is for this specific controller and it's block devices to
fail.
This way I can get the failure log message and actually do something
with that data without rebooting.
Or I guess digital cameras and serial/net consoles are the only
sanctioned way to record kernel failure log messages of this kind?
Give me a break. :)
next prev parent reply other threads:[~2009-01-16 19:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-16 14:56 [GIT PATCH] firs round of SCSI bug fixes for 2.6.29-rc1 James Bottomley
2009-01-16 17:09 ` Andrew Morton
2009-01-16 18:48 ` James Bottomley
2009-01-16 19:07 ` Andrew Morton
2009-01-16 20:28 ` James Bottomley
2009-01-16 19:09 ` David Miller [this message]
2009-01-16 19:02 ` Grant Grundler
2009-01-16 19:10 ` David Miller
2009-01-16 20:09 ` Grant Grundler
2009-01-16 20:15 ` James Bottomley
2009-01-17 21:17 ` Matthew Wilcox
2009-02-11 4:08 ` Matthew Wilcox
2009-02-11 12:42 ` James Bottomley
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=20090116.110931.166270342.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=James.Bottomley@HansenPartnership.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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