Re: [PATCH 2/2] libnvdimm: clear region badblock in nvdimm_clear_poison()

2017-05-01 Thread Kani, Toshimitsu
On Fri, 2017-04-28 at 17:35 -0700, Dan Williams wrote: > On Fri, Apr 28, 2017 at 5:12 PM, Dan Williams om> wrote: > > On Fri, Apr 28, 2017 at 5:10 PM, Dan Williams > .com> wrote: > > > On Thu, Apr 27, 2017 at 3:57 PM, Toshi Kani

Re: [PATCH 2/2] libnvdimm: clear region badblock in nvdimm_clear_poison()

2017-05-01 Thread Kani, Toshimitsu
On Fri, 2017-04-28 at 17:35 -0700, Dan Williams wrote: > On Fri, Apr 28, 2017 at 5:12 PM, Dan Williams om> wrote: > > On Fri, Apr 28, 2017 at 5:10 PM, Dan Williams > .com> wrote: > > > On Thu, Apr 27, 2017 at 3:57 PM, Toshi Kani > > > wrote: > > > > Badblocks are tracked at both region and

Re: [PATCH 2/2] libnvdimm: clear region badblock in nvdimm_clear_poison()

2017-04-28 Thread Dan Williams
On Fri, Apr 28, 2017 at 5:12 PM, Dan Williams wrote: > On Fri, Apr 28, 2017 at 5:10 PM, Dan Williams > wrote: >> On Thu, Apr 27, 2017 at 3:57 PM, Toshi Kani wrote: >>> Badblocks are tracked at both region and device

Re: [PATCH 2/2] libnvdimm: clear region badblock in nvdimm_clear_poison()

2017-04-28 Thread Dan Williams
On Fri, Apr 28, 2017 at 5:12 PM, Dan Williams wrote: > On Fri, Apr 28, 2017 at 5:10 PM, Dan Williams > wrote: >> On Thu, Apr 27, 2017 at 3:57 PM, Toshi Kani wrote: >>> Badblocks are tracked at both region and device levels. >>> pmem_clear_poison() and nsio_rw_bytes() call nvdimm_clear_poison()

Re: [PATCH 2/2] libnvdimm: clear region badblock in nvdimm_clear_poison()

2017-04-28 Thread Dan Williams
On Fri, Apr 28, 2017 at 5:10 PM, Dan Williams wrote: > On Thu, Apr 27, 2017 at 3:57 PM, Toshi Kani wrote: >> Badblocks are tracked at both region and device levels. >> pmem_clear_poison() and nsio_rw_bytes() call nvdimm_clear_poison() >> and then

Re: [PATCH 2/2] libnvdimm: clear region badblock in nvdimm_clear_poison()

2017-04-28 Thread Dan Williams
On Fri, Apr 28, 2017 at 5:10 PM, Dan Williams wrote: > On Thu, Apr 27, 2017 at 3:57 PM, Toshi Kani wrote: >> Badblocks are tracked at both region and device levels. >> pmem_clear_poison() and nsio_rw_bytes() call nvdimm_clear_poison() >> and then badblocks_clear() to clear badblocks at the

Re: [PATCH 2/2] libnvdimm: clear region badblock in nvdimm_clear_poison()

2017-04-28 Thread Dan Williams
On Thu, Apr 27, 2017 at 3:57 PM, Toshi Kani wrote: > Badblocks are tracked at both region and device levels. > pmem_clear_poison() and nsio_rw_bytes() call nvdimm_clear_poison() > and then badblocks_clear() to clear badblocks at the device level. > However, it does not update

Re: [PATCH 2/2] libnvdimm: clear region badblock in nvdimm_clear_poison()

2017-04-28 Thread Dan Williams
On Thu, Apr 27, 2017 at 3:57 PM, Toshi Kani wrote: > Badblocks are tracked at both region and device levels. > pmem_clear_poison() and nsio_rw_bytes() call nvdimm_clear_poison() > and then badblocks_clear() to clear badblocks at the device level. > However, it does not update badblocks at the

[PATCH 2/2] libnvdimm: clear region badblock in nvdimm_clear_poison()

2017-04-27 Thread Toshi Kani
Badblocks are tracked at both region and device levels. pmem_clear_poison() and nsio_rw_bytes() call nvdimm_clear_poison() and then badblocks_clear() to clear badblocks at the device level. However, it does not update badblocks at the region level, which makes them inconsistent. Change

[PATCH 2/2] libnvdimm: clear region badblock in nvdimm_clear_poison()

2017-04-27 Thread Toshi Kani
Badblocks are tracked at both region and device levels. pmem_clear_poison() and nsio_rw_bytes() call nvdimm_clear_poison() and then badblocks_clear() to clear badblocks at the device level. However, it does not update badblocks at the region level, which makes them inconsistent. Change