linux-kernel - Re: tmpfs and the OOM killer

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: <200704121208.57807.linux_user@izecksohn.com>
Date:	Thu, 12 Apr 2007 12:08:57 -0300
From:	Pedro <linux_user@...cksohn.com>
To:	linux-kernel@...r.kernel.org
Subject: Re: tmpfs and the OOM killer

I wrote:
> >   I deduce that a fail-safe application must scanf overcommit_memory,
> > warn the user and waitpid.

Alan Cox wrote:
> If you are building a fail safe system you need to look a bit beyond out
> of memory handling settings - power supplies, failover, fault tolerance
> requirements, error detection (eg ECC ram), raid arrays over
> non-electrically conductive links etc.

  If you lived here, you'ld be worried about seismic-electric impact on your 
HDD and data ;) So SIGKILL is not the hardest problem to be solved.

  Maybe it is time to write an avoidoomd.
-
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/