linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Ian Kent <raven@themaw.net>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	autofs mailing list <autofs@vger.kernel.org>,
	Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 04/13] autofs4 - change printks AUTOFS defined prints
Date: Mon, 03 Nov 2014 00:25:36 -0800	[thread overview]
Message-ID: <1415003136.17743.9.camel@perches.com> (raw)
In-Reply-To: <20141103081234.6215.82821.stgit@perseus.themaw.net>

On Mon, 2014-11-03 at 16:12 +0800, Ian Kent wrote:
> Use the AUTOFS_*() print defines instead of raw printks.

Please check the output of these conversions.

For instance:

> diff --git a/fs/autofs4/waitq.c b/fs/autofs4/waitq.c
[]
> @@ -162,7 +162,7 @@ static void autofs4_notify_daemon(struct autofs_sb_info *sbi,
>  		break;
>  	}
>  	default:
> -		printk("autofs4_notify_daemon: bad type %d!\n", type);
> +		AUTOFS_WARN("autofs4_notify_daemon: bad type %d!", type);
>  		mutex_unlock(&sbi->wq_mutex);
>  		return;
>  	}

The current #define is:

#define AUTOFS_WARN(fmt, ...)                          \
	pr_warn("pid %d: %s: " fmt "\n",        \
		current->pid, __func__, ##__VA_ARGS__)
 
So this duplicates the function name in the output.

It's probably better to simply use
	#define pr_fmt(fmt) KBUILD_MODNAME ": " fmt
or
	#define pr_fmt(fmt) KBUILD_MODNAME ":%d:%s" fmt, current->pid, __func__
if you _really_ want pid/func in the output

and just use pr_<level> instead of AUTOFS_<LEVEL> macros.

And it's better to use a consistent style for
these logging functions ideally with terminating
newlines so there isn't a mix of code with
and without those newlines.  That inconsistency
leads to unintended defects.



  reply	other threads:[~2014-11-03  8:25 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-03  8:12 [PATCH 01/13] autofs4 - coding style fixes Ian Kent
2014-11-03  8:12 ` [PATCH 02/13] autofs4 - fix some white space errors Ian Kent
2014-11-03  8:12 ` [PATCH 03/13] autofs4 - use pr print in AUTOFS prints Ian Kent
2014-11-03  8:12 ` [PATCH 04/13] autofs4 - change printks AUTOFS defined prints Ian Kent
2014-11-03  8:25   ` Joe Perches [this message]
2014-11-03  9:20     ` Ian Kent
2014-11-03 14:33       ` Joe Perches
2014-11-05 23:02         ` Ian Kent
2014-11-05 23:20           ` Joe Perches
2014-11-05 23:42             ` Ian Kent
2014-11-03  8:12 ` [PATCH 05/13] autofs4 - fix string.h include in auto_dev-ioctl.h Ian Kent
2014-11-03  8:12 ` [PATCH 06/13] autofs4 - move linux/auto_dev-ioctl.h to uapi/linux Ian Kent
2014-11-03  8:12 ` [PATCH 07/13] autofs - merge auto_fs.h and auto_fs4.h Ian Kent
2014-11-03  8:12 ` [PATCH 08/13] autofs - use autofs instead of autofs4 everywhere Ian Kent
2014-11-03  8:13 ` [PATCH 09/13] autofs - copy autofs4 to autofs Ian Kent
2014-11-03  8:13 ` [PATCH 10/13] autofs - create autofs Kconfig and Makefile Ian Kent
2014-11-03  8:13 ` [PATCH 11/13] autofs - update fs/autofs4/Kconfig Ian Kent
2014-11-03  8:13 ` [PATCH 12/13] autofs - update fs/autofs4/Makefile Ian Kent
2014-11-03  8:13 ` [PATCH 13/13] autofs - delete fs/autofs4 source files Ian Kent

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=1415003136.17743.9.camel@perches.com \
    --to=joe@perches.com \
    --cc=akpm@linux-foundation.org \
    --cc=autofs@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=raven@themaw.net \
    /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;
as well as URLs for NNTP newsgroup(s).