stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dakshaja Uppalapati <dakshaja@chelsio.com>
To: eduard@hasenleithner.at, kbusch@kernel.org, sagi@grimberg.me, hch@lst.de
Cc: stable@vger.kernel.org, nirranjan@chelsio.com,
	bharat@chelsio.com, dakshaja@chelsio.com
Subject: [PATCH for-stable nvmet 0/6] nvme: Fix for blk_update_request IO error.
Date: Thu, 11 Jun 2020 21:23:33 +0530	[thread overview]
Message-ID: <20200611155339.9429-1-dakshaja@chelsio.com> (raw)

The below error is seen in dmesg, while formatting the disks discovered on host.

dmesg:
        [  636.733374] blk_update_request: I/O error, dev nvme4n1, sector 0 op 0x3:(DISCARD) flags 0x800 phys_seg 1 prio class 0

Patch 6 fixes it and there are 5 other dependent patches that also need to be 
pulled from upstream to stable, 5.4 and 4.19 branches.

Patch 1 dependent patch

Patch 2 dependent patch

Patch 3 dependent patch

Patch 4 dependent patch

Patch 5 dependent patch

Patch 6 fix patch

Thanks,
Dakshaja


Christoph Hellwig (5):
  nvmet: Cleanup discovery execute handlers
  nvmet: Introduce common execute function for get_log_page and identify
  nvmet: Introduce nvmet_dsm_len() helper
  nvmet: Remove the data_len field from the nvmet_req struct
  nvmet: Open code nvmet_req_execute()

Sagi Grimberg (1):
  nvmet: fix dsm failure when payload does not match sgl descriptor

 drivers/nvme/target/admin-cmd.c   | 128 +++++++++++++++++-------------
 drivers/nvme/target/core.c        |  23 ++++--
 drivers/nvme/target/discovery.c   |  62 +++++++--------
 drivers/nvme/target/fabrics-cmd.c |  15 +++-
 drivers/nvme/target/fc.c          |   4 +-
 drivers/nvme/target/io-cmd-bdev.c |  19 +++--
 drivers/nvme/target/io-cmd-file.c |  20 +++--
 drivers/nvme/target/loop.c        |   2 +-
 drivers/nvme/target/nvmet.h       |  11 ++-
 drivers/nvme/target/rdma.c        |   4 +-
 drivers/nvme/target/tcp.c         |   6 +-
 11 files changed, 176 insertions(+), 118 deletions(-)

-- 
2.18.0.232.gb7bd9486b.dirty


             reply	other threads:[~2020-06-11 15:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-11 15:53 Dakshaja Uppalapati [this message]
2020-06-11 15:53 ` [PATCH for-stable nvmet 1/6] nvmet: Cleanup discovery execute handlers Dakshaja Uppalapati
2020-06-11 15:53 ` [PATCH for-stable nvmet 2/6] nvmet: Introduce common execute function for get_log_page and identify Dakshaja Uppalapati
2020-06-11 15:53 ` [PATCH for-stable nvmet 3/6] nvmet: Introduce nvmet_dsm_len() helper Dakshaja Uppalapati
2020-06-11 15:53 ` [PATCH for-stable nvmet 4/6] nvmet: Remove the data_len field from the nvmet_req struct Dakshaja Uppalapati
2020-06-11 15:53 ` [PATCH for-stable nvmet 5/6] nvmet: Open code nvmet_req_execute() Dakshaja Uppalapati
2020-06-11 15:53 ` [PATCH for-stable nvmet 6/6] nvmet: fix dsm failure when payload does not match sgl descriptor Dakshaja Uppalapati
2020-06-17 13:54 ` [PATCH for-stable nvmet 0/6] nvme: Fix for blk_update_request IO error Dakshaja Uppalapati
2020-06-17 14:15 ` Keith Busch
2020-06-22 11:21   ` Dakshaja Uppalapati
2020-06-29 13:55     ` Dakshaja Uppalapati
2020-09-04 11:33     ` Greg KH

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=20200611155339.9429-1-dakshaja@chelsio.com \
    --to=dakshaja@chelsio.com \
    --cc=bharat@chelsio.com \
    --cc=eduard@hasenleithner.at \
    --cc=hch@lst.de \
    --cc=kbusch@kernel.org \
    --cc=nirranjan@chelsio.com \
    --cc=sagi@grimberg.me \
    --cc=stable@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 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).