linux-kernel - Re: kmemtrace.txt question: kernel parameter(s)?

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]

Date:	Fri, 18 Dec 2009 08:57:49 +0800
From:	Li Zefan <lizf@...fujitsu.com>
To:	Randy Dunlap <randy.dunlap@...cle.com>
CC:	lkml <linux-kernel@...r.kernel.org>, eduard.munteanu@...ux360.ro,
	Pekka Enberg <penberg@...helsinki.fi>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Ingo Molnar <mingo@...e.hu>
Subject: Re: kmemtrace.txt question: kernel parameter(s)?

Randy Dunlap wrote:
> Hi,
> 
> Documentation/trace/kmemtrace.txt says:
> 
> Q: 'cat /sys/kernel/debug/kmemtrace/total_overruns' is non-zero, how do I fix
> this? Should I worry?
> A: If it's non-zero, this affects kmemtrace's accuracy, depending on how
> large the number is. You can fix it by supplying a higher
> 'kmemtrace.subbufs=N' kernel parameter.
> 
> 
> Where is this kernel parameter implemented and where is it documented?
> or should this Answer just be fixed?
> 

The whole documentation is out-dated. The original kmemtrace was based on
relay, and then it moved to ftrace, without updating the documentation.
--
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/