public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Erez Zadok <ezk@cs.sunysb.edu>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
	linux-fsdevel@vger.kernel.org, viro@ftp.linux.org.uk,
	hch@infradead.org
Subject: Re: [PATCH 1/3] Unionfs: use printk KERN_CONT for debugging messages
Date: Wed, 02 Jan 2008 22:26:20 -0800	[thread overview]
Message-ID: <1199341581.6615.39.camel@localhost> (raw)
In-Reply-To: <1199339862303-git-send-email-ezk@cs.sunysb.edu>

On Thu, 2008-01-03 at 00:57 -0500, Erez Zadok wrote:
> diff --git a/fs/unionfs/debug.c b/fs/unionfs/debug.c
> index c2b8b58..5f1d887 100644
> --- a/fs/unionfs/debug.c
> +++ b/fs/unionfs/debug.c
>  void __show_inode_times(const struct inode *inode,
> @@ -472,15 +473,15 @@ void __show_inode_times(const struct inode *inode,
>  		if (unlikely(!lower_inode))
>  			continue;
>  		pr_debug("IT(%lu:%d): ", inode->i_ino, bindex);
> -		pr_debug("%s:%s:%d ", file, fxn, line);
> -		pr_debug("um=%lu/%lu lm=%lu/%lu ",
> -			 inode->i_mtime.tv_sec, inode->i_mtime.tv_nsec,
> -			 lower_inode->i_mtime.tv_sec,
> -			 lower_inode->i_mtime.tv_nsec);
> -		pr_debug("uc=%lu/%lu lc=%lu/%lu\n",
> -			 inode->i_ctime.tv_sec, inode->i_ctime.tv_nsec,
> -			 lower_inode->i_ctime.tv_sec,
> -			 lower_inode->i_ctime.tv_nsec);
> +		printk(KERN_CONT "%s:%s:%d ", file, fxn, line);
> +		printk(KERN_CONT "um=%lu/%lu lm=%lu/%lu ",
> +		       inode->i_mtime.tv_sec, inode->i_mtime.tv_nsec,
> +		       lower_inode->i_mtime.tv_sec,
> +		       lower_inode->i_mtime.tv_nsec);
> +		printk(KERN_CONT "uc=%lu/%lu lc=%lu/%lu\n",
> +		       inode->i_ctime.tv_sec, inode->i_ctime.tv_nsec,
> +		       lower_inode->i_ctime.tv_sec,
> +		       lower_inode->i_ctime.tv_nsec);
>  	}
>  }
>  

I think printks should be single statements and
KERN_CONT should be used as sparingly as possible.

Perhaps:
		pr_debug("IT(%lu:%d): %s:%s:%d "
			 "um=%lu/%lu lm=%lu/%lu "
			 "uc=%lu/%lu lc=%lu/%lu\n",
			 inode->i_ino, bindex, file, fnx, line,
			 inode->i_mtime.tv_sec, inode->i_mtime.tv_nsec,
			 lower_inode->i_mtime.tv_sec,
			 lower_inode->i_mtime.tv_nsec
			 inode->i_ctime.tv_sec, inode->i_ctime.tv_nsec,
			 lower_inode->i_ctime.tv_sec,
			 lower_inode->i_ctime.tv_nsec);

> @@ -497,15 +498,15 @@ void __show_dinode_times(const struct dentry *dentry,
>  			continue;
>  		pr_debug("DT(%s:%lu:%d): ", dentry->d_name.name, inode->i_ino,
>  			 bindex);
> -		pr_debug("%s:%s:%d ", file, fxn, line);
> -		pr_debug("um=%lu/%lu lm=%lu/%lu ",
> -			 inode->i_mtime.tv_sec, inode->i_mtime.tv_nsec,
> -			 lower_inode->i_mtime.tv_sec,
> -			 lower_inode->i_mtime.tv_nsec);
> -		pr_debug("uc=%lu/%lu lc=%lu/%lu\n",
> -			 inode->i_ctime.tv_sec, inode->i_ctime.tv_nsec,
> -			 lower_inode->i_ctime.tv_sec,
> -			 lower_inode->i_ctime.tv_nsec);
> +		printk(KERN_CONT "%s:%s:%d ", file, fxn, line);
> +		printk(KERN_CONT "um=%lu/%lu lm=%lu/%lu ",
> +		       inode->i_mtime.tv_sec, inode->i_mtime.tv_nsec,
> +		       lower_inode->i_mtime.tv_sec,
> +		       lower_inode->i_mtime.tv_nsec);
> +		printk(KERN_CONT "uc=%lu/%lu lc=%lu/%lu\n",
> +		       inode->i_ctime.tv_sec, inode->i_ctime.tv_nsec,
> +		       lower_inode->i_ctime.tv_sec,
> +		       lower_inode->i_ctime.tv_nsec);
>  	}
>  }
>  

and
		pr_debug("DT(%s:%lu:%d): %s:%s:%d "
			 "um=%lu/%lu lm=%lu/%lu "
			 "uc=%lu/%lu lc=%lu/%lu\n",
			 dentry->d_name.name, inode->i_ino, bindex,
			 file, fnx, line,
			 inode->i_mtime.tv_sec, inode->i_mtime.tv_nsec,
			 lower_inode->i_mtime.tv_sec,
			 lower_inode->i_mtime.tv_nsec
			 inode->i_ctime.tv_sec, inode->i_ctime.tv_nsec,
			 lower_inode->i_ctime.tv_sec,
			 lower_inode->i_ctime.tv_nsec);

> 
> @@ -524,9 +525,10 @@ void __show_inode_counts(const struct inode *inode,
>  		lower_inode = unionfs_lower_inode_idx(inode, bindex);
>  		if (unlikely(!lower_inode))
>  			continue;
> -		pr_debug("SIC(%lu:%d:%d): ", inode->i_ino, bindex,
> -			 atomic_read(&(inode)->i_count));
> -		pr_debug("lc=%d ", atomic_read(&(lower_inode)->i_count));
> -		pr_debug("%s:%s:%d\n", file, fxn, line);
> +		printk(KERN_CONT "SIC(%lu:%d:%d): ", inode->i_ino, bindex,
> +		       atomic_read(&(inode)->i_count));
> +		printk(KERN_CONT "lc=%d ",
> +		       atomic_read(&(lower_inode)->i_count));
> +		printk(KERN_CONT "%s:%s:%d\n", file, fxn, line);
>  	}
>  }

and
		pr_debug("SIC(%lu:%d:%d): lc=%d %s:%s:%d\n",
			 inode->i_ino, bindex,
			 atomic_read(&(inode)->i_count),
			 atomic_read(&(lower_inode)->i_count),
			 file, fxn, line);


  reply	other threads:[~2008-01-03  6:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-03  5:57 [GIT PULL -mm] 0/3 Unionfs updates/fixes/cleanups Erez Zadok
2008-01-03  5:57 ` [PATCH 1/3] Unionfs: use printk KERN_CONT for debugging messages Erez Zadok
2008-01-03  6:26   ` Joe Perches [this message]
2008-01-03 18:36     ` Erez Zadok
2008-01-03  5:57 ` [PATCH 2/3] Unionfs: locking fixes Erez Zadok
2008-01-03  5:57 ` [PATCH 3/3] Unionfs: use VFS helpers to manipulate i_nlink Erez Zadok

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=1199341581.6615.39.camel@localhost \
    --to=joe@perches.com \
    --cc=akpm@linux-foundation.org \
    --cc=ezk@cs.sunysb.edu \
    --cc=hch@infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@ftp.linux.org.uk \
    /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