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: Thu, 07 Apr 2016 16:36:16 -0400 (EDT) From: David Miller <davem@...emloft.net> To: dhowells@...hat.com Cc: joe@...ches.com, linux-afs@...ts.infradead.org, netdev@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH 2/9] rxrpc: Disable a debugging statement that has been left enabled. From: David Howells <dhowells@...hat.com> Date: Thu, 07 Apr 2016 20:45:08 +0100 > David Miller <davem@...emloft.net> wrote: > >> Yeah this custom stuff is really inappropriate given the excellent >> infrastructure we have these days... > > Excellent only if I can get at it to find out why the something went wrong. > If it's lost because the machine panics, then it is worthless. If you're ok with these kenter things spewing into the logs with the current facility, you can run the function tracer and have it record into the logs all the time too. I don't see any argument which is appropriate for keeping this stuff around.
Powered by blists - more mailing lists