All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: Szabolcs Szakacsits <szaka@f-secure.com>
Cc: Rik van Riel <riel@conectiva.com.br>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	Linus Torvalds <torvalds@transmeta.com>,
	Ingo Molnar <mingo@elte.hu>
Subject: Re: KPATCH] Reserve VM for root (was: Re: Looking for better VM)
Date: Sat, 18 Nov 2000 21:49:06 +0100	[thread overview]
Message-ID: <20001118214906.D382@bug.ucw.cz> (raw)
In-Reply-To: <200011142012.VAA00150@bug.ucw.cz> <Pine.LNX.4.30.0011161513480.20626-100000@fs129-190.f-secure.com>
In-Reply-To: <Pine.LNX.4.30.0011161513480.20626-100000@fs129-190.f-secure.com>; from Szabolcs Szakacsits on Thu, Nov 16, 2000 at 04:01:07PM +0100

Hi!

> >    >main() { while(1) if (fork()) malloc(1); }
> >    >With the patch below I could ssh to the host and killall the offending
> >    >processes. To enable reserving VM space for root do
> > what about main() { while(1) system("ftp localhost &"); }
> > This. or so,ething similar should allow you to kill your machine
> > even with your patch from normal user account
> 
> This or something similar didn't kill the box [I've tried all local
> DoS from Packetstorm that I could find]. Please send a working

Sorry, I did not have working example, just feeling that something
like that should be possible.

> Note, I'm not discussing "local user can kill the box without limits",
> I say Linux "deadlocks" [it starts its own autonom life and usually
> your only chance is to hit the reset button] when there is continuous
> VM pressure by user applications. If you think fork() kills the box

That's clear bug, right? It should not deadlock, it should go to
OOM-killer and kill someone.

> BTW, I have a new version of the patch with that Linux behaves much
> better from root's point of view when the memory is more significantly
> overcommited. I'll post it if I have time [and there is interest].

There is interest. Yesterday atrey died due userland process eating
all memory.
								Pavel
PS: atrey is machine that gets my mail, so it is kind of important to
me.
-- 
I'm pavel@ucw.cz. "In my country we have almost anarchy and I don't care."
Panos Katsaloulis describing me w.r.t. patents at discuss@linmodems.org
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

WARNING: multiple messages have this Message-ID (diff)
From: Pavel Machek <pavel@suse.cz>
To: Szabolcs Szakacsits <szaka@f-secure.com>
Cc: Rik van Riel <riel@conectiva.com.br>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	Linus Torvalds <torvalds@transmeta.com>,
	Ingo Molnar <mingo@elte.hu>
Subject: Re: KPATCH] Reserve VM for root (was: Re: Looking for better VM)
Date: Sat, 18 Nov 2000 21:49:06 +0100	[thread overview]
Message-ID: <20001118214906.D382@bug.ucw.cz> (raw)
In-Reply-To: <Pine.LNX.4.30.0011161513480.20626-100000@fs129-190.f-secure.com>; from Szabolcs Szakacsits on Thu, Nov 16, 2000 at 04:01:07PM +0100

Hi!

> >    >main() { while(1) if (fork()) malloc(1); }
> >    >With the patch below I could ssh to the host and killall the offending
> >    >processes. To enable reserving VM space for root do
> > what about main() { while(1) system("ftp localhost &"); }
> > This. or so,ething similar should allow you to kill your machine
> > even with your patch from normal user account
> 
> This or something similar didn't kill the box [I've tried all local
> DoS from Packetstorm that I could find]. Please send a working

Sorry, I did not have working example, just feeling that something
like that should be possible.

> Note, I'm not discussing "local user can kill the box without limits",
> I say Linux "deadlocks" [it starts its own autonom life and usually
> your only chance is to hit the reset button] when there is continuous
> VM pressure by user applications. If you think fork() kills the box

That's clear bug, right? It should not deadlock, it should go to
OOM-killer and kill someone.

> BTW, I have a new version of the patch with that Linux behaves much
> better from root's point of view when the memory is more significantly
> overcommited. I'll post it if I have time [and there is interest].

There is interest. Yesterday atrey died due userland process eating
all memory.
								Pavel
PS: atrey is machine that gets my mail, so it is kind of important to
me.
-- 
I'm pavel@ucw.cz. "In my country we have almost anarchy and I don't care."
Panos Katsaloulis describing me w.r.t. patents at discuss@linmodems.org
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/

  parent reply	other threads:[~2000-11-18 22:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-01-02  6:21 KPATCH] Reserve VM for root (was: Re: Looking for better VM) pavel-velo
1997-01-02  6:21 ` pavel-velo
2000-11-16 15:01 ` Szabolcs Szakacsits
2000-11-16 15:01   ` Szabolcs Szakacsits
2000-11-16 15:51   ` Rik van Riel
2000-11-16 15:51     ` Rik van Riel
2000-11-16 16:03     ` Christoph Hellwig
2000-11-16 16:03       ` Christoph Hellwig
2000-11-16 16:05       ` Rik van Riel
2000-11-16 16:05         ` Rik van Riel
2000-11-16 21:33     ` Szabolcs Szakacsits
2000-11-16 21:33       ` Szabolcs Szakacsits
2000-11-18 20:49   ` Pavel Machek [this message]
2000-11-18 20:49     ` Pavel Machek

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=20001118214906.D382@bug.ucw.cz \
    --to=pavel@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mingo@elte.hu \
    --cc=riel@conectiva.com.br \
    --cc=szaka@f-secure.com \
    --cc=torvalds@transmeta.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.