From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=0.2 required=5.0 tests=BAYES_00,INVALID_MSGID,
	REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,93db2bcd4637d4fc
X-Google-Attributes: gid103376,public
From: kilgallen@eisner.decus.org (Larry Kilgallen)
Subject: Re: Runtime Error with gnat 3.10p
Date: 1998/05/28
Message-ID: <1998May27.203126.1@eisner>#1/1
X-Deja-AN: 357144741
X-Nntp-Posting-Host: eisner.decus.org
References: <Pine.GSO.3.96.980526140456.402A-100000@bree.teisa.unican.es>
 <6kel87$ic7$1@polo.advicom.net> <356AF4B7.5EBF8617@cl.cam.ac.uk>
 <dewar.896294071@merv>
X-Trace: news.decus.org 896315490 1585 KILGALLEN [192.67.173.2]
Organization: LJK Software
Reply-To: Kilgallen@eisner.decus.org.nospam
Newsgroups: comp.lang.ada
Date: 1998-05-28T00:00:00+00:00
List-Id: <comp.lang.ada>


In article <dewar.896294071@merv>, dewar@merv.cs.nyu.edu (Robert Dewar) writes:
> <<Under Linux, the RM Annex D real-time task priorities can only be fully
> implemented on top of POSIX.1c threads if the process is running with
> root privileges. Otherwise, a malicious non-root process could lock-up
> the entire system by requesting FIFO_Queuing and going into an
> endless loop (in other words, you do not want full Annex D
> compliance for normal untrusted users on a multi-user system).
>>>
> 
> Annex D cannot  be blamed here. it is perfectly possible to implement
> full compliance with annex D without giving a proogram to seize the
> system in this manner. Annex D talks about relationship of tasks
> in your Ada program, not about their relation to other programs runningf
> on the same operating system.

The phrase "Under Linux" would seem to have exonerated Annex D by
implying there existed one or more other operating systems where
reasonable implementation on top of POSIX.1c threads was possible.

Larry Kilgallen