linux-kernel - Suggested code code : simple : keep simple out-of-memory (oom) msg without rate

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

Message-Id: <1C11DCE4-A4EF-42AC-BFB7-5B06190482C4@earthlink.net>
Date:	Fri, 10 Jul 2009 19:13:18 -0700
From:	Mitchell Erblich <erblichs@...thlink.net>
To:	linux-kernel@...r.kernel.org
Subject: Suggested code code : simple : keep simple out-of-memory (oom) msg without rate_limits

Group,


	Out of memory (oom) process killer is invoked when there is EXTREME  
memory stress.

	With the understanding that anytime we kill a process, a minimal  
amount of information
	about the process should be kept to be able to backtrack why a system  
may be currently
	be running with less than a normal level of functionality.

	Thus, ./mm/oom_kill.c : oom_kill_process()

	This change limits the amount of printing while keeping the coarse  
level of info
	when a process is killed within one function. The later function  
calls generate
	multiple times of output than the one printk that we are keeping.

	move the if (printf_ratelimit() ) { statement to after the printk  
invoked oom-killer

	2ndly, should the not / " ! "  be stated within the ratelimit check?

	Mitchell Erblich
	FYI: This CHANGE is one of a set of simple set of changes AND is my  
"due-dilligence" of what was partially done
	        for a company and due to ... was not submitted back to  
Linux.org. The major section re-writes are not being
	        submitted at this time.
	
	
--
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/