From: Toshi Kani <toshi.kani@hpe.com> To: dan.j.williams@intel.com Cc: linux-kernel@vger.kernel.org, linux-nvdimm@lists.01.org Subject: [PATCH] libnvdimm: fix phys_addr for nvdimm_clear_poison Date: Tue, 25 Apr 2017 15:16:51 -0600 [thread overview] Message-ID: <20170425211651.7640-1-toshi.kani@hpe.com> (raw) nvdimm_clear_poison() expects a physical address, not an offset. Fix nsio_rw_bytes() to call nvdimm_clear_poison() with a physical address. Signed-off-by: Toshi Kani <toshi.kani@hpe.com> Cc: Dan Williams <dan.j.williams@intel.com> Cc: Dave Jiang <dave.jiang@intel.com> Cc: Vishal Verma <vishal.l.verma@intel.com> --- drivers/nvdimm/claim.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/drivers/nvdimm/claim.c b/drivers/nvdimm/claim.c index ca6d572..0b31073 100644 --- a/drivers/nvdimm/claim.c +++ b/drivers/nvdimm/claim.c @@ -254,7 +254,8 @@ static int nsio_rw_bytes(struct nd_namespace_common *ndns, && (!ndns->claim || !is_nd_btt(ndns->claim))) { long cleared; - cleared = nvdimm_clear_poison(&ndns->dev, offset, size); + cleared = nvdimm_clear_poison(&ndns->dev, + nsio->res.start + offset, size); if (cleared < size) rc = -EIO; if (cleared > 0 && cleared / 512) { _______________________________________________ Linux-nvdimm mailing list Linux-nvdimm@lists.01.org https://lists.01.org/mailman/listinfo/linux-nvdimm
WARNING: multiple messages have this Message-ID (diff)
From: Toshi Kani <toshi.kani@hpe.com> To: dan.j.williams@intel.com Cc: dave.jiang@intel.com, vishal.l.verma@intel.com, linux-nvdimm@ml01.01.org, linux-kernel@vger.kernel.org, Toshi Kani <toshi.kani@hpe.com> Subject: [PATCH] libnvdimm: fix phys_addr for nvdimm_clear_poison Date: Tue, 25 Apr 2017 15:16:51 -0600 [thread overview] Message-ID: <20170425211651.7640-1-toshi.kani@hpe.com> (raw) nvdimm_clear_poison() expects a physical address, not an offset. Fix nsio_rw_bytes() to call nvdimm_clear_poison() with a physical address. Signed-off-by: Toshi Kani <toshi.kani@hpe.com> Cc: Dan Williams <dan.j.williams@intel.com> Cc: Dave Jiang <dave.jiang@intel.com> Cc: Vishal Verma <vishal.l.verma@intel.com> --- drivers/nvdimm/claim.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/drivers/nvdimm/claim.c b/drivers/nvdimm/claim.c index ca6d572..0b31073 100644 --- a/drivers/nvdimm/claim.c +++ b/drivers/nvdimm/claim.c @@ -254,7 +254,8 @@ static int nsio_rw_bytes(struct nd_namespace_common *ndns, && (!ndns->claim || !is_nd_btt(ndns->claim))) { long cleared; - cleared = nvdimm_clear_poison(&ndns->dev, offset, size); + cleared = nvdimm_clear_poison(&ndns->dev, + nsio->res.start + offset, size); if (cleared < size) rc = -EIO; if (cleared > 0 && cleared / 512) {
next reply other threads:[~2017-04-25 21:17 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-04-25 21:16 Toshi Kani [this message] 2017-04-25 21:16 ` [PATCH] libnvdimm: fix phys_addr for nvdimm_clear_poison Toshi Kani 2017-04-25 21:44 ` Vishal Verma 2017-04-25 21:44 ` Vishal Verma 2017-04-25 21:49 ` Kani, Toshimitsu 2017-04-25 21:49 ` Kani, Toshimitsu 2017-04-25 22:22 ` Vishal Verma 2017-04-25 22:22 ` Vishal Verma 2017-04-25 22:57 ` Dan Williams 2017-04-25 22:57 ` Dan Williams
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=20170425211651.7640-1-toshi.kani@hpe.com \ --to=toshi.kani@hpe.com \ --cc=dan.j.williams@intel.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-nvdimm@lists.01.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: linkBe 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.