linux-kernel - Re: [BUG?] OOM with large cache....(x86

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: <20071120054648.GA20436@elte.hu>
Date:	Tue, 20 Nov 2007 06:46:48 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Nick Piggin <nickpiggin@...oo.com.au>
Cc:	pomac@...or.com, Linux-kernel@...r.kernel.org
Subject: Re: [BUG?] OOM with large cache....(x86_64, 2.6.24-rc3-git1, nohz)

* Nick Piggin <nickpiggin@...oo.com.au> wrote:

> Unfortunately, we don't show NR_ANON_PAGES in these stats, [...]

sidenote: the way i combat these missing pieces of instrumentation in 
the scheduler is to add them immediately to the cfs-debug-info.sh script 
(and to /proc/sched_debug if needed). I.e. if we get one report that 
misses a piece of critical information is OK, but if it's two reports 
and we still havent made it easy to report the right kind of information 
that is our fault entirely. This constant ping-ponging for information 
that goes on for basically every MM problem - which information could 
have been provided in the first message (by running a single, easy to 
download tool) is getting pretty hindering i believe.

	Ingo
-
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/