Messages in this thread | | | Date | Fri, 30 Mar 2007 19:24:47 -0700 (PDT) | From | Linus Torvalds <> | Subject | Re: [patch 1/13] signal/timer/event fds v8 - anonymous inode source ... |
| |
On Fri, 30 Mar 2007, Andrew Morton wrote: > > > > Ok, it was panincing, and someone made me change it. Would you please > > agree? > > The system can survive w/out, but it'll be a broken system WRT userspace. > > I'd say panic. There's no much point in limping along with an > incorrectly-working kernel, only to have some small number of apps fail > mysteriously later on.
Well, in this case (since it's at bootup only), I'd agree with panic(), but generally I disagree - it's actually much better to have a broken system limping along and allowing things like syslogd to write the problem to log-files and generally working as well as possible.
If people can do a "dmesg" and send it out as an email, we're much more likely to get good bug-reports.
But for early boot, and for something that can't really happen anyway, panic() sounds fine.
Linus - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |