linux-kernel - Re: super root shell/mode/api

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

Date:	Wed, 20 May 2009 07:03:27 +0100
From:	Sitsofe Wheeler <sitsofe@...oo.com>
To:	Willy Tarreau <w@....eu>
Cc:	Henrique de Moraes Holschuh <hmh@....eng.br>,
	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Andrea <andrea256it@...oo.it>, linux-kernel@...r.kernel.org
Subject: Re: super root shell/mode/api

On Wed, May 20, 2009 at 06:36:04AM +0200, Willy Tarreau wrote:
> 
> I don't know if mainline distros do this, but some distros dedicated to
> embedded systems have been using that for ages, almost since Alan published
> his first overcommit patch a long time ago. It's the only way to reach
> very long uptimes on servers, as it also protects you against your own
> mistakes (eg: stupid actions such as "vi access.log" when the file is
> larger than memory).

Shouldn't the vi case be taken care of by good ulimits? Certainly that's
what I've seen openSUSE do by default (although strangely SLES 10
doesn't)...

The last I heard about overcommit was that there were always some
legitimate programs that could run that would be stopped by having it on
(evolution always seemed to be mentioned for some reason). As such it
would be surprising to see any of the desktop distros enabling it by
default.

I've been wondering for a while with my EeePC if strict overcommit is a
no brainer if you are running without swap... In such systems the only
things that can be forced out of RAM are mmap'd files (?) so does
overcommit even happen?

-- 
Sitsofe | http://sucs.org/~sits/
--
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/