From: Chris Wright <chris@wirex.com>
To: Luis Miguel Correia Henriques <umiguel@alunos.deis.isec.pt>
Cc: linux-kernel@vger.kernel.org
Subject: Re: copy to user
Date: Tue, 20 Nov 2001 14:05:48 -0800 [thread overview]
Message-ID: <20011120140548.A12208@figure1.int.wirex.com> (raw)
In-Reply-To: <Pine.LNX.4.31.0111202040180.23000-100000@mail.deis.isec.pt>
In-Reply-To: <Pine.LNX.4.31.0111202040180.23000-100000@mail.deis.isec.pt>; from umiguel@alunos.deis.isec.pt on Tue, Nov 20, 2001 at 08:54:42PM +0000
* Luis Miguel Correia Henriques (umiguel@alunos.deis.isec.pt) wrote:
> The reason that I need it to spend CPU time is that I'm developing a fault
> injector. The purpose of a fault injection tool is, as you could imagine,
> to test some critical systems and it's capacity to recover from fails. The
> reason for changing the code of a process is that process must be delayed
> but without leaving the CPU - everything must look like nothing wrong is
> happening, except for other processes that are waiting for something from
> the delayed process...
with ptrace(2) you can write into the program's .bss, whatever...add a
little shellcode and you're dangerous ;-)
-chris
next prev parent reply other threads:[~2001-11-20 22:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-20 20:54 copy to user Luis Miguel Correia Henriques
2001-11-20 21:28 ` John Alvord
2001-11-20 21:44 ` Andreas Dilger
2001-11-21 11:02 ` Luís Henriques
2001-11-20 22:02 ` n0ano
2001-11-20 22:05 ` Chris Wright [this message]
2001-11-21 8:43 ` Mathijs Mohlmann
2001-11-21 10:12 ` Jan Hudec
-- strict thread matches above, loose matches on Subject: below --
2001-11-25 21:58 Marco C. Mason
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=20011120140548.A12208@figure1.int.wirex.com \
--to=chris@wirex.com \
--cc=linux-kernel@vger.kernel.org \
--cc=umiguel@alunos.deis.isec.pt \
/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