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]

Message-Id: <20090116.111059.205876014.davem@davemloft.net>
Date:	Fri, 16 Jan 2009 11:10:59 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	grundler@...gle.com
Cc:	akpm@...ux-foundation.org, James.Bottomley@...senpartnership.com,
	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: Grant Grundler <grundler@...gle.com>
Date: Fri, 16 Jan 2009 11:02:12 -0800

> On Fri, Jan 16, 2009 at 9:09 AM, Andrew Morton
> <akpm@...ux-foundation.org> wrote:
> ...
> >> +             CHIPREG_WRITE32(&ioc->chip->Doorbell, 0xC0FFEE00);
> >> +             panic("%s: Firmware is halted due to command timeout\n",
> >> +                     ioc->name);
> >> +     }
> >> +}
> >> +EXPORT_SYMBOL(mpt_halt_firmware);
> >
> > 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?
> 
> Basically what James said. It's not long though: only 6 emails.
> I started that thread thinking the same thing you did:
>     http://marc.info/?t=123123569200003&r=1&w=2
> 
> TBH, I still wouldn't implement it the way LSI maintainers did.
> I'm happy they are the maintainers and it's their call.

They are doing things which effect the entire system, not just
their driver.  So this doesn't fall under "maintainer's rights"

If they fail locally, that's fine and perfectly expected, but to take
the whole machine out is another matter altogether.
--
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/