From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: Victor Porton <porton@ex-code.com>, Avi Kivity <avi@argo.co.il>,
linux-kernel@vger.kernel.org, Jesper Juhl <jesper.juhl@gmail.com>
Subject: Re: New reliability technique
Date: Sun, 26 Feb 2006 23:30:36 +1100 [thread overview]
Message-ID: <44019F6C.4020400@yahoo.com.au> (raw)
In-Reply-To: <84144f020602260425p70fc4c5cn6de8dd6aa8a876d7@mail.gmail.com>
Pekka Enberg wrote:
> On 2/26/06, Victor Porton <porton@ex-code.com> wrote:
>
>>Isn't it better to double check (especially after such risky things as
>>e.g. software suspend)?
>>
>>We need to check not only for damaged hardware, but also for
>>kernel/modules bugs. For this ECC and cache reliability is useless.
>
>
> What kernel bugs do you want to catch with double-checking free
> memory? For use-after-free, we already have slab poisoning.
>
And for !slab, we unmap kernel virtual addresses with page debugging,
which seems like a better solution.
--
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com
prev parent reply other threads:[~2006-02-26 12:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-25 13:21 New reliability technique Victor Porton
2006-02-25 13:26 ` Jesper Juhl
2006-02-25 13:27 ` Jesper Juhl
2006-02-25 19:52 ` Avi Kivity
2006-02-25 19:56 ` Jesper Juhl
2006-02-25 22:44 ` Janos Farkas
2006-02-26 11:34 ` Victor Porton
2006-02-26 12:25 ` Pekka Enberg
2006-02-26 12:30 ` Nick Piggin [this message]
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=44019F6C.4020400@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=avi@argo.co.il \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
--cc=porton@ex-code.com \
/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).