| 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
| ||
|
Message-Id: <1193336900.5697.14.camel@localhost.localdomain> Date: Thu, 25 Oct 2007 19:28:20 +0100 From: Richard Purdie <rpurdie@...ys.net> To: Alan Cox <alan@...rguk.ukuu.org.uk> Cc: LKML <linux-kernel@...r.kernel.org> Subject: Re: Linux machines dieing in swap storms On Thu, 2007-10-25 at 17:13 +0100, Alan Cox wrote: > > 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. I couldn't seem to find much documentation on this. For the archive and to confirm we're talking about the same thing, you mean: echo 10 > /proc/PID/oom_adj (and ulimit/setrlimit for the resource limits) ? This assumes I know in advance which processes are likely to go mad which isn't ideal although it could solve my immediate problem. > 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. Its certainly another option but other processes then suffer because certain applications have bugs in them? Thanks, Richard - 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/
Powered by blists - more mailing lists