linux-kernel - Re: [GIT PATCH] firs round of SCSI bug fixes for 2.6.29-rc1

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:	Fri, 16 Jan 2009 11:09:31 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	James.Bottomley@...senPartnership.com
Cc:	akpm@...ux-foundation.org, torvalds@...ux-foundation.org,
	linux-scsi@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [GIT PATCH] firs round of SCSI bug fixes for 2.6.29-rc1

From: James Bottomley <James.Bottomley@...senPartnership.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. :)
--
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/