Messages in this thread | | | Date | Sun, 26 Feb 2006 14:25:25 +0200 | From | "Pekka Enberg" <> | Subject | Re: New reliability technique |
| |
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.
Pekka - 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/
| |