From: "Kani, Toshimitsu" <toshi.kani@hpe.com>
To: "dan.j.williams@intel.com" <dan.j.williams@intel.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>
Subject: Re: [PATCH 1/2] libnvdimm: fix clear length of nvdimm_forget_poison()
Date: Fri, 28 Apr 2017 22:29:16 +0000 [thread overview]
Message-ID: <1493418523.30303.6.camel@hpe.com> (raw)
In-Reply-To: <CAPcyv4i+U62GMyK=xNXB9ZjzS-028q4Qch=kxa9_pkwXrFJdsA@mail.gmail.com>
On Fri, 2017-04-28 at 14:48 -0700, Dan Williams wrote:
> On Thu, Apr 27, 2017 at 3:57 PM, Toshi Kani <toshi.kani@hpe.com>
> wrote:
> > ND_CMD_CLEAR_ERROR command returns 'clear_err.cleared', the length
> > of error actually cleared, which may be smaller than its requested
> > 'len'.
> >
> > Change nvdimm_clear_poison() to call nvdimm_forget_poison() with
> > 'clear_err.cleared' when this value is valid.
> >
> > 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>
> > ---
> > Based on 'libnvdimm-for-next'.
> > ---
> > drivers/nvdimm/bus.c | 4 +++-
> > 1 file changed, 3 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/nvdimm/bus.c b/drivers/nvdimm/bus.c
> > index d214ac44..43ddfd4 100644
> > --- a/drivers/nvdimm/bus.c
> > +++ b/drivers/nvdimm/bus.c
> > @@ -219,7 +219,9 @@ long nvdimm_clear_poison(struct device *dev,
> > phys_addr_t phys,
> > if (cmd_rc < 0)
> > return cmd_rc;
> >
> > - nvdimm_forget_poison(nvdimm_bus, phys, len);
> > + if (clear_err.cleared > 0)
> > + nvdimm_forget_poison(nvdimm_bus, phys,
> > clear_err.cleared);
> > +
> > return clear_err.cleared;
>
> Looks, good we need to mark this for -stable since the bug is also
> present in current mainline.
>
> Fixes: e046114af5fc ("libnvdimm: clear the internal poison_list when
> clearing badblocks")
Shall I send a patch based on the current mainline with cc to -stable?
The func name is nvdimm_clear_from_poison_list() in the mainline.
Thanks,
-Toshi
_______________________________________________
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: "Kani, Toshimitsu" <toshi.kani@hpe.com>
To: "dan.j.williams@intel.com" <dan.j.williams@intel.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"dave.jiang@intel.com" <dave.jiang@intel.com>,
"linux-nvdimm@lists.01.org" <linux-nvdimm@ml01.01.org>,
"vishal.l.verma@intel.com" <vishal.l.verma@intel.com>
Subject: Re: [PATCH 1/2] libnvdimm: fix clear length of nvdimm_forget_poison()
Date: Fri, 28 Apr 2017 22:29:16 +0000 [thread overview]
Message-ID: <1493418523.30303.6.camel@hpe.com> (raw)
In-Reply-To: <CAPcyv4i+U62GMyK=xNXB9ZjzS-028q4Qch=kxa9_pkwXrFJdsA@mail.gmail.com>
On Fri, 2017-04-28 at 14:48 -0700, Dan Williams wrote:
> On Thu, Apr 27, 2017 at 3:57 PM, Toshi Kani <toshi.kani@hpe.com>
> wrote:
> > ND_CMD_CLEAR_ERROR command returns 'clear_err.cleared', the length
> > of error actually cleared, which may be smaller than its requested
> > 'len'.
> >
> > Change nvdimm_clear_poison() to call nvdimm_forget_poison() with
> > 'clear_err.cleared' when this value is valid.
> >
> > 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>
> > ---
> > Based on 'libnvdimm-for-next'.
> > ---
> > drivers/nvdimm/bus.c | 4 +++-
> > 1 file changed, 3 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/nvdimm/bus.c b/drivers/nvdimm/bus.c
> > index d214ac44..43ddfd4 100644
> > --- a/drivers/nvdimm/bus.c
> > +++ b/drivers/nvdimm/bus.c
> > @@ -219,7 +219,9 @@ long nvdimm_clear_poison(struct device *dev,
> > phys_addr_t phys,
> > if (cmd_rc < 0)
> > return cmd_rc;
> >
> > - nvdimm_forget_poison(nvdimm_bus, phys, len);
> > + if (clear_err.cleared > 0)
> > + nvdimm_forget_poison(nvdimm_bus, phys,
> > clear_err.cleared);
> > +
> > return clear_err.cleared;
>
> Looks, good we need to mark this for -stable since the bug is also
> present in current mainline.
>
> Fixes: e046114af5fc ("libnvdimm: clear the internal poison_list when
> clearing badblocks")
Shall I send a patch based on the current mainline with cc to -stable?
The func name is nvdimm_clear_from_poison_list() in the mainline.
Thanks,
-Toshi
next prev parent reply other threads:[~2017-04-28 22:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-27 22:57 [PATCH 1/2] libnvdimm: fix clear length of nvdimm_forget_poison() Toshi Kani
2017-04-27 22:57 ` Toshi Kani
2017-04-27 22:57 ` [PATCH 2/2] libnvdimm: clear region badblock in nvdimm_clear_poison() Toshi Kani
2017-04-27 22:57 ` Toshi Kani
2017-04-29 0:10 ` Dan Williams
2017-04-29 0:10 ` Dan Williams
2017-04-29 0:12 ` Dan Williams
2017-04-29 0:12 ` Dan Williams
2017-04-29 0:35 ` Dan Williams
2017-04-29 0:35 ` Dan Williams
2017-05-01 15:05 ` Kani, Toshimitsu
2017-05-01 15:05 ` Kani, Toshimitsu
2017-04-28 21:48 ` [PATCH 1/2] libnvdimm: fix clear length of nvdimm_forget_poison() Dan Williams
2017-04-28 21:48 ` Dan Williams
2017-04-28 22:29 ` Kani, Toshimitsu [this message]
2017-04-28 22:29 ` Kani, Toshimitsu
2017-04-28 22:39 ` Dan Williams
2017-04-28 22:39 ` Dan Williams
2017-04-28 22:41 ` Kani, Toshimitsu
2017-04-28 22:41 ` Kani, Toshimitsu
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=1493418523.30303.6.camel@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: 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.