Re: Local Linux Crash (fwd)

From: Mike Galbraith (mikeg@weiden.de)
Date: Sat Mar 25 2000 - 08:12:47 EST


On Sat, 25 Mar 2000, Kurt Roeckx wrote:

> On Sat, Mar 25, 2000 at 07:23:12AM +0100, Mike Galbraith wrote:
> > On Fri, 24 Mar 2000, ADAM Sulmicki wrote:
> >
> > > FYI.
> > >
> > > I'm just messenger.
> > > I saw it on bugtraq and would pass it.
> > > Don't shoot me
> > > :-)
> > >
> > > ---------- Forwarded message ----------
> > > Date: Fri, 24 Mar 2000 18:42:03 +0200
> > > From: Javor Ninov <javor@multigroup-bg.com>
> > > To: BUGTRAQ@SECURITYFOCUS.COM
> > > Subject: Local Linux Crash
> > >
> > > Tested on SlackWare 7.0 2.2.14
> > > After short time this will crash Linux box:
> > > su `cat /dev/urandom` > /dev/null |< su `cat /dev/urandom`&
> > >
> > > for a better efect start it several times :-))
> > > This can be done be any regular user !
> >
> > On 2.3.99x at least, this only acts as a resource hog. After setting
> > limits, bash grew steadily until...
> >
> > bash: xrealloc: cannot reallocate 4194304 bytes (0 bytes allocated)
> >
> > ...and then politely exited.
>
> I started it 5 times, no limits. The first 3 did that too.
>
> Then VM killed 1 bash, and then killed klogd every second, couldn't do a
> thing with the system anymore.
>
> This was using 2.3.51

You let it go OOM. That shouldn't kill the box though (loops forever
trying to send signal). I tested a patch from Andrea which cured this
'toothless tiger' problem.. guess it didn't make it in.

        -Mike

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/



This archive was generated by hypermail 2b29 : Fri Mar 31 2000 - 21:00:15 EST