From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: michaels@jungo.com (Michael Shmulevich)
Cc: macro@ds2.pg.gda.pl (Maciej W. Rozycki), linux-mips@oss.sgi.com
Subject: Re: User applications
Date: Tue, 9 Jan 2001 12:17:26 +0000 (GMT) [thread overview]
Message-ID: <E14FxiT-0006XP-00@the-village.bc.nu> (raw)
In-Reply-To: <3A5AFAC8.CA682600@jungo.com> from "Michael Shmulevich" at Jan 09, 2001 01:49:29 PM
> promoted to the syscall status? What is the situation that a user in its program
> would like
> to call cacheflush() ? Unless, of course, he is doing DoS.
A cache flush is not a denial of service attack. Its no less effective than a
1Mb memcpy
> I can understand why we need this in kernel, for context switch, for example, but
> as a syscall?...
Self modifying code, dynamic compilation, glibc trampolines
WARNING: multiple messages have this Message-ID (diff)
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Michael Shmulevich <michaels@jungo.com>
Cc: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>, linux-mips@oss.sgi.com
Subject: Re: User applications
Date: Tue, 9 Jan 2001 12:17:26 +0000 (GMT) [thread overview]
Message-ID: <E14FxiT-0006XP-00@the-village.bc.nu> (raw)
Message-ID: <20010109121726.nDBC-i8-UKG9-y5kzIeNDXsdxbAcjOEMvYmfV_9hwL8@z> (raw)
In-Reply-To: <3A5AFAC8.CA682600@jungo.com> from "Michael Shmulevich" at Jan 09, 2001 01:49:29 PM
> promoted to the syscall status? What is the situation that a user in its program
> would like
> to call cacheflush() ? Unless, of course, he is doing DoS.
A cache flush is not a denial of service attack. Its no less effective than a
1Mb memcpy
> I can understand why we need this in kernel, for context switch, for example, but
> as a syscall?...
Self modifying code, dynamic compilation, glibc trampolines
next prev parent reply other threads:[~2001-01-09 12:19 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-08 9:40 User applications Carsten Langgaard
2001-01-08 13:30 ` Michael Shmulevich
2001-01-08 13:52 ` Carsten Langgaard
2001-01-08 14:14 ` Kevin D. Kissell
2001-01-08 14:14 ` Kevin D. Kissell
2001-01-08 14:16 ` Carsten Langgaard
2001-01-08 16:03 ` Ralf Baechle
2001-01-08 15:07 ` Maciej W. Rozycki
2001-01-08 15:21 ` Kevin D. Kissell
2001-01-08 15:21 ` Kevin D. Kissell
2001-01-08 15:40 ` Maciej W. Rozycki
2001-01-08 16:27 ` Ralf Baechle
2001-01-08 16:43 ` Maciej W. Rozycki
2001-01-08 16:41 ` Ralf Baechle
2001-01-08 16:05 ` Ralf Baechle
2001-01-08 16:23 ` Carsten Langgaard
2001-01-08 16:30 ` Ralf Baechle
2001-01-08 16:50 ` Carsten Langgaard
2001-01-08 17:56 ` Maciej W. Rozycki
2001-01-08 16:40 ` Maciej W. Rozycki
2001-01-08 17:42 ` Ralf Baechle
2001-01-08 17:58 ` Maciej W. Rozycki
2001-01-09 11:49 ` Michael Shmulevich
2001-01-09 12:15 ` Geert Uytterhoeven
2001-01-09 12:17 ` Alan Cox [this message]
2001-01-09 12:17 ` Alan Cox
2001-01-09 13:00 ` Maciej W. Rozycki
2001-01-08 16:34 ` Maciej W. Rozycki
2001-01-08 14:16 ` Maciej W. Rozycki
2001-01-08 16:25 ` Ralf Baechle
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=E14FxiT-0006XP-00@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-mips@oss.sgi.com \
--cc=macro@ds2.pg.gda.pl \
--cc=michaels@jungo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox