From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: [PATCH 2/9] rxrpc: Disable a debugging statement that has been left enabled. Date: Thu, 07 Apr 2016 16:50:21 -0400 (EDT) Message-ID: <20160407.165021.1271761992369838408.davem@davemloft.net> References: <1460046677.6715.95.camel@perches.com> <1091.1460058308@warthog.procyon.org.uk> <5702.1460062039@warthog.procyon.org.uk> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: joe@perches.com, linux-afs@lists.infradead.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org To: dhowells@redhat.com Return-path: In-Reply-To: <5702.1460062039@warthog.procyon.org.uk> Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org From: David Howells Date: Thu, 07 Apr 2016 21:47:19 +0100 > David Miller wrote: > >> > 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. > > They don't do that unless you enable them. And I can enable them individually > at compile time or by set at runtime. As you can with the function tracer and tracepoints. We're not telling you to kill this now, we're just saying that you should thinking about tossing this custom stuff when you have a chance.