Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1632433 > unrolled thread

[PATCH 1/2] libnvdimm: fix clear length of nvdimm_forget_poison()

Started byToshi Kani <toshi.kani@hpe.com>
First post2017-04-28 01:00 +0200
Last post2017-04-29 00:50 +0200
Articles 5 — 3 participants

Back to article view | Back to linux.kernel

Contents

  [PATCH 1/2] libnvdimm: fix clear length of nvdimm_forget_poison() Toshi Kani <toshi.kani@hpe.com> - 2017-04-28 01:00 +0200
    Re: [PATCH 1/2] libnvdimm: fix clear length of nvdimm_forget_poison() Dan Williams <dan.j.williams@intel.com> - 2017-04-28 23:50 +0200
      Re: [PATCH 1/2] libnvdimm: fix clear length of nvdimm_forget_poison() "Kani, Toshimitsu" <toshi.kani@hpe.com> - 2017-04-29 00:30 +0200
        Re: [PATCH 1/2] libnvdimm: fix clear length of nvdimm_forget_poison() Dan Williams <dan.j.williams@intel.com> - 2017-04-29 00:40 +0200
          Re: [PATCH 1/2] libnvdimm: fix clear length of nvdimm_forget_poison() "Kani, Toshimitsu" <toshi.kani@hpe.com> - 2017-04-29 00:50 +0200

#1632433 — [PATCH 1/2] libnvdimm: fix clear length of nvdimm_forget_poison()

FromToshi Kani <toshi.kani@hpe.com>
Date2017-04-28 01:00 +0200
Subject[PATCH 1/2] libnvdimm: fix clear length of nvdimm_forget_poison()
Message-ID<tB0ye-7ca-9@gated-at.bofh.it>
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;
 }
 EXPORT_SYMBOL_GPL(nvdimm_clear_poison);

[toc] | [next] | [standalone]

#1633172

FromDan Williams <dan.j.williams@intel.com>
Date2017-04-28 23:50 +0200
Message-ID<tBlW1-51T-5@gated-at.bofh.it>
In reply to#1632433
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")

[toc] | [prev] | [next] | [standalone]

#1633189

From"Kani, Toshimitsu" <toshi.kani@hpe.com>
Date2017-04-29 00:30 +0200
Message-ID<tBmyK-5xk-11@gated-at.bofh.it>
In reply to#1633172
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

[toc] | [prev] | [next] | [standalone]

#1633191

FromDan Williams <dan.j.williams@intel.com>
Date2017-04-29 00:40 +0200
Message-ID<tBmIp-5Bh-3@gated-at.bofh.it>
In reply to#1633189
On Fri, Apr 28, 2017 at 3:29 PM, Kani, Toshimitsu <toshi.kani@hpe.com> wrote:
> 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.

I thinks it's too late to get a fix into 4.11, especially when this
went in broken and not a regression. I'll just tag this for -stable
and handle the backport manually.

[toc] | [prev] | [next] | [standalone]

#1633194

From"Kani, Toshimitsu" <toshi.kani@hpe.com>
Date2017-04-29 00:50 +0200
Message-ID<tBmS5-5Fv-1@gated-at.bofh.it>
In reply to#1633191
On Fri, 2017-04-28 at 15:39 -0700, Dan Williams wrote:
> On Fri, Apr 28, 2017 at 3:29 PM, Kani, Toshimitsu <toshi.kani@hpe.com
> > wrote:
> > 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>
 :
> > > > 
> > > > -       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.
> 
> I thinks it's too late to get a fix into 4.11, especially when this
> went in broken and not a regression. I'll just tag this for -stable
> and handle the backport manually.

Sounds great. Thanks Dan!
-Toshi

[toc] | [prev] | [standalone]

Back to top | Article view | linux.kernel

csiph-web