linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robert Elliott <elliott@hp.com>
To: axboe@kernel.dk, webbnh@hp.com, linux-kernel@vger.kernel.org,
	relliott@beardog.cce.hp.com, linux-fsdevel@vger.kernel.org,
	viro@zeniv.linux.org.uk, elliott@hp.com,
	scameron@beardog.cce.hp.com
Subject: [PATCH 2/2] block: include func name in __get_request prints
Date: Wed, 27 Aug 2014 10:50:36 -0500	[thread overview]
Message-ID: <20140827155036.32075.20577.stgit@beardog.cce.hp.com> (raw)
In-Reply-To: <20140827154628.32075.3821.stgit@beardog.cce.hp.com>

In __get_request calls to printk_ratelimited, include the function name so
the callbacks suppressed message matches the messages that are printed,
and add "dev" before the device name so it matches other block layer
messages.

Signed-off-by: Robert Elliott <elliott@hp.com>
Reviewed-by: Webb Scales <webbnh@hp.com>
---
 block/blk-core.c |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/block/blk-core.c b/block/blk-core.c
index 9c5a5b9..204cbd3 100644
--- a/block/blk-core.c
+++ b/block/blk-core.c
@@ -1065,8 +1065,8 @@ fail_elvpriv:
 	 * shouldn't stall IO.  Treat this request as !elvpriv.  This will
 	 * disturb iosched and blkcg but weird is bettern than dead.
 	 */
-	printk_ratelimited(KERN_WARNING "%s: request aux data allocation failed, iosched may be disturbed\n",
-			   dev_name(q->backing_dev_info.dev));
+	printk_ratelimited(KERN_WARNING "%s: dev %s: request aux data allocation failed, iosched may be disturbed\n",
+			   __func__, dev_name(q->backing_dev_info.dev));
 
 	rq->cmd_flags &= ~REQ_ELVPRIV;
 	rq->elv.icq = NULL;

      parent reply	other threads:[~2014-08-27 15:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-27 15:50 [PATCH 0/2] block: improve I/O error print consistency Robert Elliott
2014-08-27 15:50 ` [PATCH 1/2] block: make blk_update_request print prefix match ratelimited prefix Robert Elliott
2014-08-27 15:50 ` Robert Elliott [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=20140827155036.32075.20577.stgit@beardog.cce.hp.com \
    --to=elliott@hp.com \
    --cc=axboe@kernel.dk \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=relliott@beardog.cce.hp.com \
    --cc=scameron@beardog.cce.hp.com \
    --cc=viro@zeniv.linux.org.uk \
    --cc=webbnh@hp.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;
as well as URLs for NNTP newsgroup(s).