LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Stas Sergeev <stsp@aknet.ru>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Bug in VM accounting code, probably exploitable
Date: Sat, 22 May 2004 16:46:22 +0400	[thread overview]
Message-ID: <40AF4B9E.5000305@aknet.ru> (raw)
In-Reply-To: <20040520194358.GE19922@logos.cnet>

Hi Marcelo.

Marcelo Tosatti wrote:
>>As you can see, the program caused many
>>other processes to be killed, before it
>>died itself.
> About v2.4, can you try v2.4.26 with CONFIG_OOM_KILLER=y ? 
OK, with CONFIG_OOM_KILLER=y (2.4.26) I get this:
---
May 22 16:14:56 lin kernel: Out of Memory: Killed process 1514 
(overc_test).
May 22 16:14:56 lin kernel: Out of Memory: Killed process 1320 
(mozilla-bin).
May 22 16:14:56 lin kernel: Out of Memory: Killed process 1406 
(mozilla-bin).
May 22 16:14:56 lin kernel: Out of Memory: Killed process 1407 
(mozilla-bin).
May 22 16:14:56 lin kernel: Out of Memory: Killed process 1409 
(mozilla-bin).
---
Better than without OOM killer, although
still not perfect - for some reasons it also
decided to kill mozilla *after* killing the
test program. Strange.

> As for the overcommit, I think it has always been "broken"? (its always 
> possible to overcommit).
At least I received a couple of messages that
stated that my test program doesn't OOM the
RedHat Fedora 2.4 kernels - mprotect() fails
with ENOMEM. That resembles the correct
behaveour of the fixed 2.6 so I think at least
RedHat got rid of that problem somehow.
Hope that helps.

      reply	other threads:[~2004-05-22 12:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-11 19:50 Stas Sergeev
2004-05-11 20:45 ` Hugh Dickins
2004-05-20 19:43 ` Marcelo Tosatti
2004-05-22 12:46   ` Stas Sergeev [this message]

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=40AF4B9E.5000305@aknet.ru \
    --to=stsp@aknet.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.tosatti@cyclades.com \
    --subject='Re: Bug in VM accounting code, probably exploitable' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).