From mboxrd@z Thu Jan 1 00:00:00 1970 From: Florian Westphal Subject: Re: ip_set: protocol %u message -- useful? Date: Thu, 13 Feb 2014 20:59:08 +0100 Message-ID: <20140213195908.GK25153@breakpoint.cc> References: <20140213184254.GF14175@macbook.localnet> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Patrick McHardy , Cong Wang , Jozsef Kadlecsik , netdev , "linux-kernel@vger.kernel.org" , Vitaly Lavrov To: Ilia Mirkin Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org Ilia Mirkin wrote: > > Maybe printing "using protocol version X" will make it appear less like > > a debugging message referring to packet contents or something similar. > > With pr_info it'll still appear in dmesg, and it'll still be "random > non-sensical message appears over and over in dmesg" type of > situation, to the vast majority of users. Do we need a print every > time someone creates a new tcp connection too? I'm still not totally > clear on the cause of this message getting printed, but I was seeing > it a whole bunch in my configuration... Yes, because it erronously got moved into the netns init function. And thats what causes the spew. Moving it back into module init function should be enough.