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: 27 Mar 2007 17:19:02 +0200 From: Andi Kleen <andi@...stfloor.org> To: Wink Saville <wink@...ille.com> Cc: linux-kernel@...r.kernel.org Subject: Re: [PATCH 1/3] Documention for trace records (trec). Wink Saville <wink@...ille.com> writes: > Trec is a light weight tracing mechanism that places > trace information into a buffer. The contents of the > buffer is dumped when errors occurs or when enabled > via SYSRQ commands. relayfs was supposed to fill this purpose. Why do you want another one? It doesn't work for sysrq dumping on fatal errors, but in my experience on such cases custom tracing is best. -Andi - 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/