linux-kernel - Re: Linux machines dieing in swap storms

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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20071025171311.42844d17@the-village.bc.nu>
Date:	Thu, 25 Oct 2007 17:13:11 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Richard Purdie <rpurdie@...ys.net>
Cc:	LKML <linux-kernel@...r.kernel.org>
Subject: Re: Linux machines dieing in swap storms

> I'm seriously tempted to add a "kill the process using the most memory"
> key combination into SysRq which might let me save the desktop but won't
> help with my remote server. I could also just disable swap I guess.

For specific applications you can set resource limits, you can also set
OOM priorities in current kernels to pick who dies.

Finally you can disable overcommit and go for a rigid "no overcommit"
policy where the system will fail any memory allocation which might lead
to out of memory situations later.

Alan
-
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/