*BSD News Article 98896


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.mira.net.au!news.netspace.net.au!news.melbpc.org.au!news.mel.connect.com.au!munnari.OZ.AU!uunet!in2.uu.net!128.230.129.112!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!peer.news.nildram.co.uk!Aladdin!aladdin.net!ns2.aladdin.net!RMplc!rmplc.co.uk!yama.mcc.ac.uk!news.york.ac.uk!pih100
From: pih100@york.ac.uk (Paul Halliday)
Newsgroups: comp.unix.pc-clone.32bit,comp.unix.bsd.freebsd.misc,comp.unix.bsd.386bsd.misc,comp.os.ms-windows.nt.advocacy,comp.os.linux.x,comp.os.linux.setup,comp.os.linux.advocacy
Subject: Re: Linux needs more work to be done!
Followup-To: comp.unix.pc-clone.32bit,comp.unix.bsd.freebsd.misc,comp.unix.bsd.386bsd.misc,comp.os.ms-windows.nt.advocacy,comp.os.linux.x,comp.os.linux.setup,comp.os.linux.advocacy
Date: 2 Jul 1997 19:46:58 GMT
Organization: The University of York, UK
Lines: 33
Sender: pih100@york.ac.uk
Message-ID: <5peb7i$aqv$1@netty.york.ac.uk>
References: <5oqbad$1582@ds2.acs.ucalgary.ca> <xdoradosk1v.fsf@bagel.rs.itd.umich.edu> <xdo4taj2akk.fsf@pita.ccs.itd.umich.edu>
NNTP-Posting-Host: tower.york.ac.uk
X-Newsreader: TIN [version 1.2 PL2]
Xref: euryale.cc.adfa.oz.au comp.unix.pc-clone.32bit:9708 comp.unix.bsd.freebsd.misc:43858 comp.unix.bsd.386bsd.misc:1295 comp.os.ms-windows.nt.advocacy:64999 comp.os.linux.x:65606 comp.os.linux.setup:119474 comp.os.linux.advocacy:104160

Timothy Watson (tmwatson@pita.ccs.itd.umich.edu) wrote:
: Memory-allocation issues do exist, if you have looked at the kernel
: mailing list bit (one is the killing of system daemons, which should
: really be rewritten to be tolerant of memory allocation failures

Is this the same effect as running several callocs in an infinite loop?
e.g. For simplicity;

main()
{
	for(;;)
		calloc(10000, 8);
}

and run a number of them simultaneously in the background, then try to do
something useful like log in ...
I haven't found a kernel that reacts well to this - most crash (such as
1.1.59, 2.0.0, and everything beyond 2.1.34 that I've tried) - the ALT-F
keys work between sessions, but no sessions will respond - even CTRL-ALT-DEL 
fails to do anything.
The only one I've seen to try to stay up is 2.0.27 (I've skipped a few),
which like you describe, results in users being able to kill system
daemons, crash update and send init to the top of the processor queue (and
again render CTRL-ALT-DEL useless).

Unfortunately this hole allows anyone to break a Linux box at will which
doesn't bode well for it if run as, say, a central unix server. Personally
I broke it with a single large calloc when doing a physics project some
months ago and now worry as much about breaking Linux by doing anything
useful as I do about running any of the MS rubbish.
Considering it's always been around, it's surprising it's never been fixed. :-{

Paul.