linux-kernel - Panic on OOM

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 14 Jun 2011 09:31:16 -0400
From:	Chris Fowler <cfowler@...postsentinel.com>
To:	linux-kernel@...r.kernel.org
Subject: Panic on OOM

I'm running into a problem in 2.6.38 where the kernel is not doing what
I'm expecting it to do.  I'm guessing that some things have changed and
that is what it going on.

First,  The tune at boot:

        f.open("/proc/sys/vm/panic_on_oom", std::ios::out);
        f << "1";
        f.close();

        f.open("/proc/sys/kernel/panic", std::ios::out);
        f << "10";
        f.close();

I want the kernel to panic on out of memory.  I then want it to wait 10s
before doing a reboot.

This program will consume all memory and make the box unresponsive

#!/usr/bin/perl

my @mem = ()
while(1) {
  push @mem, "########################";
}

It does not take long to fill up 1G of space.  There is NO swap on this
device and never will be.  I did notice that after a long period of time
(I've not timed it) I finally do see a panic and I do see "rebooting in
10 seconds..." .  It does not reboot.

I'm guessing that there are some tweaks or new behavior I just need to
be aware of.

Thanks,
Chris

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