From: "Benjamin C. Ling" <bling@CS.Stanford.EDU>
To: linux-kernel@vger.kernel.org
Subject: how to inject memory bitflips for maximum damage?
Date: Sat, 23 Aug 2003 14:39:55 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.44.0308231439040.19230-100000@Xenon.Stanford.EDU> (raw)
I'm hoping there's someone here who has some knowledge on linux's
placement of objects in memory, or can point me to the right direction.
We have FAUmachine (a linux-based fault-injection VM) installed and
running on our research cluster, and can inject memory-bitflips in our
processes running on top of FAUmachine.
My question is -- how do I find out where to inject the bitflip for
maximum damage (or even any damage at all). I've done a bit of searching
on google but haven't come up with much.
If anyone has any insight on where linux holds its critical memory
structures, or where it places its running programs in physical memory,
could you please let me know?
Thanks in advance!
Ben
next reply other threads:[~2003-08-23 21:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-23 21:39 Benjamin C. Ling [this message]
2003-09-01 14:06 ` how to inject memory bitflips for maximum damage? Pavel Machek
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=Pine.LNX.4.44.0308231439040.19230-100000@Xenon.Stanford.EDU \
--to=bling@cs.stanford.edu \
--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;
as well as URLs for NNTP newsgroup(s).