Netdev List
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Yafang Shao <laoar.shao@gmail.com>, davem@davemloft.net
Cc: daniel@iogearbox.net, edumazet@google.com,
	xiyou.wangcong@gmail.com, netdev@vger.kernel.org,
	shaoyafang@didiglobal.com
Subject: Re: [PATCH v2 net-next 2/2] net: sock: undefine SOCK_DEBUGGING
Date: Sun, 17 Feb 2019 03:58:42 -0800	[thread overview]
Message-ID: <3aa310cede544d76e53ec962676a6ea4e3bd6b23.camel@perches.com> (raw)
In-Reply-To: <1550334537-380-3-git-send-email-laoar.shao@gmail.com>

On Sun, 2019-02-17 at 00:28 +0800, Yafang Shao wrote:
> SOCK_DEBUG() is a old facility for debugging.
> If the user want to use it for debugging, the user must modify the
> application first, that doesn't seem like a good way.
> Now we have more powerful facilities, i.e. bpf or tracepoint, for this kind
> of debugging purpose.
> So we'd better disable it by default.
> The reason why I don't remove it comepletely is that someone may still
> would like to use it for debugging.
> 
> Signed-off-by: Yafang Shao <laoar.shao@gmail.com>
> Suggested-by: Joe Perches <joe@perches.com>
> ---
>  include/net/sock.h | 13 ++++++++-----
>  net/core/sock.c    |  3 +++
>  2 files changed, 11 insertions(+), 5 deletions(-)
> 
> diff --git a/include/net/sock.h b/include/net/sock.h
> index 6679f3c..d41e8f4 100644
> --- a/include/net/sock.h
> +++ b/include/net/sock.h
> @@ -81,14 +81,17 @@
>   */
>  
>  /* Define this to get the SOCK_DBG debugging facility. */
> -#define SOCK_DEBUGGING
> +/* #define SOCK_DEBUGGING */
>  #ifdef SOCK_DEBUGGING
> -#define SOCK_DEBUG(sk, msg...) do { if ((sk) && sock_flag((sk), SOCK_DBG)) \
> -					printk(KERN_DEBUG msg); } while (0)
> +#define SOCK_DEBUG(sk, fmt, ...)		\
> +do {						\
> +	if ((sk) && sock_flag((sk), SOCK_DBG))	\
> +		pr_debug(fmt, ##__VA_ARGS__);	\

trivia:

I would not suggest pr_debug here as it also requires
either DEBUG to be defined or CONFIG_DYNAMIC_DEBUG
to be set.

If you really set SOCK_DEBUGGING, then printk(KERN_DEBUG
is probably right.

                                                           


  reply	other threads:[~2019-02-17 11:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-16 16:28 [PATCH v2 net-next 0/2] clean up SOCK_DEBUG() Yafang Shao
2019-02-16 16:28 ` [PATCH v2 net-next 1/2] tcp: " Yafang Shao
2019-02-16 16:28 ` [PATCH v2 net-next 2/2] net: sock: undefine SOCK_DEBUGGING Yafang Shao
2019-02-17 11:58   ` Joe Perches [this message]
2019-02-17 14:07     ` Yafang Shao

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3aa310cede544d76e53ec962676a6ea4e3bd6b23.camel@perches.com \
    --to=joe@perches.com \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=laoar.shao@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=shaoyafang@didiglobal.com \
    --cc=xiyou.wangcong@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox