| 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
| ||
|
Date: Fri, 26 Mar 2010 21:27:26 -0700 From: Randy Dunlap <randy.dunlap@...cle.com> To: Li Zefan <lizf@...fujitsu.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)? On Fri, 18 Dec 2009 08:57:49 +0800 Li Zefan wrote: > 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. Sorry for the delay. Shouldn't Documentation/trace/kmemtrace.txt just be completely deleted? It's confusing and all relevant kmemtrace documentation is elsewhere. --- ~Randy -- 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/
Powered by blists - more mailing lists