From: "Luís Henriques" <umiguel@alunos.deis.isec.pt>
To: Mike Fedyk <mfedyk@matchmail.com>,
Anton Altaparmakov <aia21@cam.ac.uk>,
linux-kernel@vger.kernel.org
Subject: Re: copy to suer space
Date: Wed, 21 Nov 2001 10:52:02 +0000 [thread overview]
Message-ID: <200111211057.fALAvi288566@criticalsoftware.com> (raw)
In-Reply-To: <5.1.0.14.2.20011120165440.00a745b0@pop.cus.cam.ac.uk> <20011120123915.W1308@lynx.no> <20011120160657.A4124@mikef-linux.matchmail.com>
In-Reply-To: <20011120160657.A4124@mikef-linux.matchmail.com>
> This to me looks like the main desire is to fool the user. It looks like
> it doing something, but it really isn't...
Not really... This may look like an old DOS virus :) but it is not! It's a
fault injection tool - it's purpose (in this case, of corse) is to cause a
very short delay on a critic process.
--
Luís Henriques
next prev parent reply other threads:[~2001-11-21 10:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.31.0111201637420.13674-100000@mail.deis.isec.pt >
2001-11-20 17:02 ` copy to suer space Anton Altaparmakov
2001-11-20 17:08 ` Luís Henriques
2001-11-20 18:41 ` Andreas Dilger
2001-11-20 18:44 ` Luís Henriques
2001-11-20 18:58 ` Hua Zhong
2001-11-20 19:39 ` Andreas Dilger
2001-11-21 0:06 ` Mike Fedyk
2001-11-21 10:52 ` Luís Henriques [this message]
2001-11-23 13:14 ` Juan Quintela
2001-11-23 14:35 ` Luís Henriques
2001-11-23 23:53 ` H. Peter Anvin
2001-11-20 17:37 ` Anton Altaparmakov
2001-11-20 17:53 ` Luís Henriques
2001-11-20 18:18 ` Nick LeRoy
2001-11-22 18:51 ` Andreas Bombe
2001-11-20 18:09 ` Luís Henriques
2001-11-21 14:37 Joerg Pommnitz
[not found] <sbfa4d3a.051@MAIL-SMTP.uvsc.edu>
2001-11-21 10:49 ` Luís Henriques
-- strict thread matches above, loose matches on Subject: below --
2001-11-20 16:40 Luis Miguel Correia Henriques
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=200111211057.fALAvi288566@criticalsoftware.com \
--to=umiguel@alunos.deis.isec.pt \
--cc=aia21@cam.ac.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mfedyk@matchmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.