From: Pavel Machek <pavel@ucw.cz>
To: Zoltan.Menyhart@bull.net
Cc: linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Dynamic System Calls & System Call Hijacking
Date: Tue, 20 Apr 2004 21:40:17 +0200 [thread overview]
Message-ID: <20040420194016.GF1413@openzaurus.ucw.cz> (raw)
In-Reply-To: <4084E85E.4722BFC6@nospam.org>
Hi!
> - Can't recompile the kernel, otherwise you gonna lose RedHat guarantee ?
> Or some ISVs like whose name starts with an "O" and terminates with "racle"
> ain't gonna support it ?
> + No problem, I'll load your syscall in a module.
Well, by forcing syscall in, you loose your guarantee, too.
cat /dev/urandom > /dev/kmem
"RedHat, help, my machine crashed."
> Your remarks will be appreciated.
I hope it at least taints the kernel.
And you did test on smp kernel, trying to race syscall calling against
your module load/unload, right?
--
64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms
next prev parent reply other threads:[~2004-04-22 19:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-20 9:07 Dynamic System Calls & System Call Hijacking Zoltan Menyhart
2004-04-20 19:40 ` Pavel Machek [this message]
2004-04-23 11:48 ` Zoltan Menyhart
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=20040420194016.GF1413@openzaurus.ucw.cz \
--to=pavel@ucw.cz \
--cc=Zoltan.Menyhart@bull.net \
--cc=linux-ia64@vger.kernel.org \
--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