All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chaitanya Kulkarni <chaitanya.kulkarni@wdc.com>
To: linux-block@vger.kernel.org
Cc: hch@lst.de, hare@suse.com,
	Chaitanya Kulkarni <chaitanya.kulkarni@wdc.com>
Subject: [PATCH 0/2] block: improve print_req_error()
Date: Tue, 11 Jun 2019 13:02:08 -0700	[thread overview]
Message-ID: <20190611200210.4819-1-chaitanya.kulkarni@wdc.com> (raw)

Hi,

This patch-series is based on the initial patch posted by 
Christoph Hellwig <hch@lst.de>. I've added one more patch to improve
further print message.

While debugging the driver and block layer this print message is very
handy.

Please consider this for 5.3.

-Chaitanya

Following is the sample error message with forced REQ_OP_WRITE failure
from null_blk:-

blk_update_request: I/O error, dev nullb0, sector 0 op 0x1:(write) flags 0x8800 phys_seg 1 prio class 0


Chaitanya Kulkarni (1):
  block: add more debug data to print_req_err

Christoph Hellwig (1):
  block: improve print_req_error

 block/blk-core.c | 67 +++++++++++++++++++++++++++++++++++++++++++-----
 1 file changed, 60 insertions(+), 7 deletions(-)

-- 
2.19.1


             reply	other threads:[~2019-06-11 20:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-11 20:02 Chaitanya Kulkarni [this message]
2019-06-11 20:02 ` [PATCH 1/2] block: improve print_req_error Chaitanya Kulkarni
2019-06-17  8:42   ` Hannes Reinecke
2019-06-17 16:49     ` Chaitanya Kulkarni
2019-06-18 11:09       ` Hannes Reinecke
2019-06-11 20:02 ` [PATCH 2/2] block: add more debug data to print_req_err Chaitanya Kulkarni
2019-06-12 15:21   ` Bart Van Assche
2019-06-12 16:19     ` Chaitanya Kulkarni

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=20190611200210.4819-1-chaitanya.kulkarni@wdc.com \
    --to=chaitanya.kulkarni@wdc.com \
    --cc=hare@suse.com \
    --cc=hch@lst.de \
    --cc=linux-block@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.