From: Denys Fedorysychenko <nuclearcat@nuclearcat.com>
To: legerde@gmail.com, linux-kernel@vger.kernel.org
Subject: Aerospace and linux
Date: Sun, 13 Jun 2010 18:26:58 +0300 [thread overview]
Message-ID: <201006131826.58146.nuclearcat@nuclearcat.com> (raw)
>Storage will probably be something really cheap. So I assume flash.
>But, possibly a USB stick type device. Maybe an IDE based solid
>state storage device.
Most of commercial controllers (USB and IDE) use intermediate cache/buffer
memory, that will be vulnerable to byte flipping (as i know even SRAM
vulnerable to that). Some of them have their own firmware, storing somewhere
chip wearing information, and if bit flipping happen there - they just will
fail (common issue: USB flash not recognized anymore or have 0 bytes
capacity).
I guess you need truly embedded device, including PCB design, and operate
with storage chips directly (RAM, flash chips). Also flash (NOR and NAND)
vulnerable to bit-flipping too, and it is prefferable to use hardened IC's (i
doubt there is hardened USB/IDE controllers), protected bus design, strong
error recovery algo's, system and parts redundancy and etc.
next reply other threads:[~2010-06-13 15:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-13 15:26 Denys Fedorysychenko [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-06-10 17:29 Brian Gordon
2010-06-10 18:23 ` Andi Kleen
2010-06-10 18:38 ` Brian Gordon
2010-06-10 18:46 ` Chris Friesen
2010-06-10 19:14 ` Brian Gordon
2010-06-10 18:48 ` Andi Kleen
2010-06-13 8:51 ` Borislav Petkov
2010-06-10 18:27 ` Chris Friesen
2010-06-10 18:42 ` Brian Gordon
2010-06-10 19:23 ` Massimiliano Galanti
2010-06-10 19:37 ` Brian Gordon
2010-06-10 19:42 ` Brian Gordon
2010-06-10 19:52 ` Massimiliano Galanti
2010-06-10 20:12 ` Brian Gordon
2010-06-10 19:59 ` Massimiliano Galanti
2010-06-11 14:37 ` Henrique de Moraes Holschuh
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=201006131826.58146.nuclearcat@nuclearcat.com \
--to=nuclearcat@nuclearcat.com \
--cc=legerde@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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
Powered by JetHome