From: Linus Torvalds <torvalds@linux-foundation.org>
To: Chris Newport <crn@netunix.com>
Cc: Ingo Molnar <mingo@elte.hu>, Christoph Lameter <clameter@sgi.com>,
Michal Piotrowski <michal.k.k.piotrowski@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
"Cherwin R. Nooitmeer" <cherwin@gmail.com>,
linux-pcmcia@lists.infradead.org,
Robert de Rooy <robert.de.rooy@gmail.com>,
Alan Cox <alan@redhat.com>, Tejun Heo <htejun@gmail.com>,
sparclinux@vger.kernel.org, David Miller <davem@davemloft.net>,
Mikael Pettersson <mikpe@it.uu.se>,
linux1394-devel@lists.sourceforge.net,
Stefan Richter <stefanr@s5r6.in-berlin.de>,
Kristian H?gsberg <krh@bitplanet.net>,
linux-pm@lists.linux-foundation.org,
"Rafael J. Wysocki" <rjw@sisk.pl>, Pavel Machek <pavel@ucw.cz>,
Marcus Better <marcus@better.se>,
Andrey Borzenkov <arvidjaar@mail.ru>,
linux-usb-devel@lists.sourceforge.net,
Greg Kroah-Hartman <gregkh@suse.de>
Subject: Re: [2/3] 2.6.22-rc2: known regressions v2
Date: Fri, 25 May 2007 09:45:28 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.0.98.0705250937550.26602@woody.linux-foundation.org> (raw)
In-Reply-To: <4656CE39.8050800@netunix.com>
On Fri, 25 May 2007, Chris Newport wrote:
>
> Maybe we should take a hint from Solaris.
No. Solaris is shit. They make their decisions based on "we control the
hardware" kind of setup.
> If the kernel crashes Solaris dumps core to swap and sets a flag.
> At the next boot this image is copied to /var/adm/crashdump where
> it is preserved for future debugging. Obviously swap needs to be
> larger than core, but this is usually the case.
(a) it's not necessarily the case at all on many systems
(b) _most_ crashes that are real BUG()'s (rather than WARN_ON()'s) leave
the system in such a fragile state that trying to write to disk is the
_last_ thing you should do.
Linux does the right thing: it tries to not make bugs fatal.
Generally, you should see an oops, and things continue. Or a
WARN_ON(), and things continue. But you should avoid the "the machine
is now dead" cases.
(c) have you looked at the size of drivers lately? I'd argue that *most*
bugs by far happen in something driver-related, and most of our source
code is likely drivers.
Writing to disk when the biggest problem is a driver to begin with
is INSANE.
So the fact is, Solaris is crap, and to a large degree Solaris is crap
exactly _because_ it assumes that it runs in a "controlled environment".
Yes, in a controlled environment, dumping the whole memory image to disk
may be the right thing to do. BUT: in a controlled environment, you'll
never get the kind of usage that Linux gets. Why do you think Linux (and
Windows, for that matter) took away a lot of the market from traditional
UNIX?
Answer: the traditional UNIX hardware/control model doesn't _work_. People
want more flexibility, both on a hardware side and on a usage side. And
once you have the flexibility, the "dump everything to disk" is simply not
an option any more.
Disk dumps etc are options at things like wall street. But look at the bug
reports, and ask yourself how many of them happen at Wall Street, and how
many of them would even be _relevant_ to somebody there?
So forget about it. The whole model is totally broken. We need to make
bug-reports short and sweet, enough so that random people can
copy-and-paste them into an email or take a digital photo. Anything else
IS TOTALLY INSANE AND USELESS!
Linus
next prev parent reply other threads:[~2007-05-25 16:47 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <46558708.2040803@googlemail.com>
2007-05-24 14:04 ` Michal Piotrowski
2007-05-24 14:18 ` [linux-pm] " Alan Stern
2007-05-24 17:01 ` Christoph Lameter
2007-05-24 17:12 ` Linus Torvalds
2007-05-24 17:18 ` Christoph Lameter
2007-05-24 18:49 ` Andrew Morton
2007-05-24 19:21 ` Linus Torvalds
2007-05-24 21:02 ` Jeff Garzik
2007-05-24 19:37 ` Ingo Molnar
2007-05-24 19:50 ` Linus Torvalds
2007-05-24 20:02 ` David Woodhouse
2007-05-25 10:11 ` Ingo Molnar
2007-05-25 10:18 ` Stefan Richter
2007-05-25 16:21 ` Linus Torvalds
2007-05-25 11:53 ` Chris Newport
2007-05-25 12:34 ` Ingo Molnar
2007-05-25 16:33 ` Andrew Morton
2007-05-25 16:45 ` Christoph Lameter
2007-05-28 3:46 ` Vivek Goyal
2007-05-25 12:40 ` Stefan Richter
2007-05-25 16:45 ` Linus Torvalds [this message]
2007-05-25 17:03 ` Alan Cox
2007-05-25 17:19 ` Linus Torvalds
2007-05-25 17:37 ` Andrew Morton
2007-05-25 17:48 ` Alan Cox
2007-05-25 17:50 ` Linus Torvalds
2007-05-28 4:27 ` Vivek Goyal
2007-05-25 17:07 ` Chuck Ebbert
2007-05-25 17:21 ` Linus Torvalds
2007-05-25 18:03 ` Chris Newport
2007-05-25 20:36 ` David Miller
2007-05-26 13:16 ` [linux-pm] " Matt Sealey
2007-06-03 6:47 ` Stefan Richter
2007-05-24 14:04 ` [3/3] " Michal Piotrowski
2007-05-24 22:04 ` Greg KH
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=alpine.LFD.0.98.0705250937550.26602@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=alan@redhat.com \
--cc=arvidjaar@mail.ru \
--cc=cherwin@gmail.com \
--cc=clameter@sgi.com \
--cc=crn@netunix.com \
--cc=davem@davemloft.net \
--cc=gregkh@suse.de \
--cc=htejun@gmail.com \
--cc=krh@bitplanet.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pcmcia@lists.infradead.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=marcus@better.se \
--cc=michal.k.k.piotrowski@gmail.com \
--cc=mikpe@it.uu.se \
--cc=mingo@elte.hu \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
--cc=robert.de.rooy@gmail.com \
--cc=sparclinux@vger.kernel.org \
--cc=stefanr@s5r6.in-berlin.de \
/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
all inboxes | Powered by JetHome®