From: Adrian Tritschler <ajft@ajft.org>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] pineview atom
Date: Fri, 19 Feb 2010 10:12:10 +1100 [thread overview]
Message-ID: <166806221002181512x13dc3662jf5b3fc00cfda529e@mail.gmail.com> (raw)
In-Reply-To: <3e7b6e1bef809d34385dcee260bdb7db@coraid.com>
On 19 February 2010 09:38, erik quanstrom <quanstro@labs.coraid.com> wrote:
>> There is no mechanism which directly translates bit flips
>> to crashes! The bad case is actually a corruption which
>> does *not* cause a crash, but is written to disk. How
> indirection? executable code being turned into illegal
> instructions? it's not 100% efficiency but it will translate
> flipped bits into crashes.
I believe Dave was implying that there is no mechanism that
_guarantees_ that a bit flip anywhere in memory will result in a code
crash. Some bit flips just might mean the wrong colour pixel on your
screen, others might mean that someone's pay scale goes from $7.50 an
hour to $4096 + $17.50 an hour, some might just be in an unused chunk
of RAM. Flips in code are more likely to cause crashes, but still not
guaranteed.
> - erik
--
Adrian
next prev parent reply other threads:[~2010-02-18 23:12 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-18 16:56 erik quanstrom
2010-02-18 18:26 ` matt
2010-02-18 18:31 ` ron minnich
2010-02-18 18:43 ` Patrick Kelly
2010-02-18 20:04 ` David Leimbach
2010-02-18 18:39 ` erik quanstrom
2010-02-18 20:46 ` ron minnich
2010-02-18 21:03 ` erik quanstrom
2010-02-18 21:14 ` Dave Eckhardt
2010-02-18 22:38 ` erik quanstrom
2010-02-18 23:08 ` roger peppe
2010-02-18 23:12 ` Adrian Tritschler [this message]
2010-02-18 23:27 ` ron minnich
2010-02-19 21:59 ` Dave Eckhardt
2010-02-20 22:17 ` erik quanstrom
2010-02-21 19:46 ` Dave Eckhardt
2010-03-05 10:01 ` hugh
2010-03-05 17:32 ` Dave Eckhardt
2010-02-18 18:43 ` Corey Thomasson
2010-03-08 17:57 ` Albert Skye
2010-03-08 19:06 ` erik quanstrom
2010-03-08 19:47 ` Jonas Amoson
2010-03-08 20:11 ` erik quanstrom
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=166806221002181512x13dc3662jf5b3fc00cfda529e@mail.gmail.com \
--to=ajft@ajft.org \
--cc=9fans@9fans.net \
/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;
as well as URLs for NNTP newsgroup(s).