public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Roman Fietze <roman.fietze@telemotive.de>
Cc: Jason Baron <jbaron@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] hex_dump_dbg: replace all calls to print_hex_dump with level KERN_DEBUG
Date: Tue, 01 Feb 2011 17:27:37 -0800	[thread overview]
Message-ID: <1296610057.4425.50.camel@Joe-Laptop> (raw)
In-Reply-To: <201102011348.18978.roman.fietze@telemotive.de>

On Tue, 2011-02-01 at 13:48 +0100, Roman Fietze wrote:
> And here, just in case it's wanted or needed, a bigger patch replacing
> all print_hex_dump calls using KERN_DEBUG.

[]

I think a lot of these changes are senseless.

print_hex_dump is a perfectly good call and doesn't
always need to be replaced by something else.

For instance:

> diff --git a/net/atm/lec.c b/net/atm/lec.c
> index 38754fd..6be1be1 100644
> --- a/net/atm/lec.c
> +++ b/net/atm/lec.c
> @@ -318,8 +318,8 @@ static netdev_tx_t lec_start_xmit(struct sk_buff *skb,
>  #if DUMP_PACKETS >= 1
>  	printk(KERN_DEBUG "%s: send datalen:%ld lecid:%4.4x\n",
>  	       dev->name, skb->len, priv->lecid);
> -	print_hex_dump(KERN_DEBUG, "", DUMP_OFFSET, 16, 1,
> -		       skb->data, min(skb->len, MAX_DUMP_SKB), true);
> +	hex_dump_dbg("", DUMP_OFFSET, 16, 1,
> +		     skb->data, min(skb->len, MAX_DUMP_SKB), true);

print_hex_dump is already guarded by an #if block.
Adding another DEBUG guard and optional on/off
control does not add any utility.

> diff --git a/net/ceph/messenger.c b/net/ceph/messenger.c
[]
> @@ -2390,19 +2390,19 @@ void ceph_msg_dump(struct ceph_msg *msg)
>  {
>  	pr_debug("msg_dump %p (front_max %d nr_pages %d)\n", msg,
>  		 msg->front_max, msg->nr_pages);
> -	print_hex_dump(KERN_DEBUG, "header: ",
> -		       DUMP_PREFIX_OFFSET, 16, 1,
> -		       &msg->hdr, sizeof(msg->hdr), true);
> -	print_hex_dump(KERN_DEBUG, " front: ",
> -		       DUMP_PREFIX_OFFSET, 16, 1,
> -		       msg->front.iov_base, msg->front.iov_len, true);
> +	hex_dump_dbg("header: ",
> +		     DUMP_PREFIX_OFFSET, 16, 1,
> +		     &msg->hdr, sizeof(msg->hdr), true);
> +	hex_dump_dbg(" front: ",
> +		     DUMP_PREFIX_OFFSET, 16, 1,
> +		     msg->front.iov_base, msg->front.iov_len, true);

These are sensible, as there is no other guard and
the immediately preceding message uses pr_debug and so
these uses should not always be output.

Could you please not just do
s/print_hex_dump(KERN_DEBUG, /hex_dump_dbg(/g
and inspect each instance for appropriateness.




      reply	other threads:[~2011-02-02  1:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-03 14:17 [PATCH] Proposal to add dynamic debug feature for print_hex_dump [0/3] Roman Fietze
2010-12-03 14:19 ` [PATCH] Proposal to add dynamic debug feature for print_hex_dump [1/2] Roman Fietze
2010-12-03 20:35   ` Joe Perches
2010-12-03 14:21 ` [PATCH] Proposal to add dynamic debug feature for print_hex_dump [2/2] Roman Fietze
2010-12-03 20:37   ` Joe Perches
2010-12-06  5:58     ` Roman Fietze
2010-12-06  6:04       ` Joe Perches
     [not found] ` <201012061113.01576.roman.fietze@telemotive.de>
     [not found]   ` <1291822758.1240.8.camel@Joe-Laptop>
2011-01-14  8:43     ` [PATCH] Proposal to add dynamic debug feature for print_hex_dump Roman Fietze
2011-01-14 18:19       ` Joe Perches
2011-02-01 12:45         ` [PATCH 0/2] Fixed proposal " Roman Fietze
2011-02-01 12:46           ` [PATCH 1/2] printk.h dynamic_debug.h: add hex_dump_<level> macros Roman Fietze
2011-02-01 12:48           ` [PATCH 2/2] hex_dump_dbg: replace all calls to print_hex_dump with level KERN_DEBUG Roman Fietze
2011-02-02  1:27             ` Joe Perches [this message]

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=1296610057.4425.50.camel@Joe-Laptop \
    --to=joe@perches.com \
    --cc=jbaron@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=roman.fietze@telemotive.de \
    /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