linux-kernel - System hang problem.

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, 3 Oct 2006 15:07:52 -0700
From:	"Manish Neema" <Manish.Neema@...opsys.com>
To:	<linux-kernel@...r.kernel.org>
Subject: System hang problem.

Sorry, I've lost my patience with RedHat so posting here....

We see this problem frequently on RHEL3.0 U5 and U7. System would
completely hang upon memory shortage. The only option left is
power-cycle (or 'sysrq + b'). System hang occurs with any of the below 3
overcommit settings:

   - default (heuristic) overcommit (overcommit_memory=0) 
   - no overcommit handling by kernel (overcommit_memory=1)
   - restrictive overcommit with ratio=100% (overcommit_memory=2;
overcommit_ratio=100)

RHEL3.0 U3 would generate an OOM kill "each and every time" it sensed
system hang but due to other bugs, we had to move away from it. RedHat
calls the timely (at least for us) invocation of OOM in U3 a buggy
implementation and the delayed OOM kill in U5 and U7 the right
implementation (which we rarely get to see resulting in at least 5
systems hanging daily!)

Changing overcommit to 2 (and ratio to any where from 1 to 99) would
result in certain OS processes (automount daemon for e.g.) getting
killed when all the allowed memory is committed. What is the point in
reserving some memory if a random root process would get killed leaving
the system in a totally unknown state?

Any suggestions on how we can prevent system-hang + not have automount
(and any other root process) die? 

TIA,
-Manish Neema

P.S. Sorry, we cannot move away from RHEL3.0 U7 for a while.
-
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/