[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CS1PR84MB0104A87F4AAB23AADF88656282C60@CS1PR84MB0104.NAMPRD84.PROD.OUTLOOK.COM>
Date: Sat, 17 Jun 2017 00:35:52 +0000
From: "Kani, Toshimitsu" <toshi.kani@....com>
To: Dan Williams <dan.j.williams@...el.com>
CC: Vishal L Verma <vishal.l.verma@...el.com>,
"Knippers, Linda" <linda.knippers@....com>,
"linux-nvdimm@...ts.01.org" <linux-nvdimm@...ts.01.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH v2] libnvdimm, pmem: Add sysfs notifications to badblocks
> On Mon, Jun 12, 2017 at 3:25 PM, Toshi Kani <toshi.kani@....com> wrote:
> > Sysfs "badblocks" information may be updated during run-time that:
> > - MCE, SCI, and sysfs "scrub" may add new bad blocks
> > - Writes and ioctl() may clear bad blocks
> >
> > Add support to send sysfs notifications to sysfs "badblocks" file
> > under region and pmem directories when their badblocks information
> > is re-evaluated (but is not necessarily changed) during run-time.
> >
> > Signed-off-by: Toshi Kani <toshi.kani@....com>
> > Cc: Dan Williams <dan.j.williams@...el.com>
> > Cc: Vishal Verma <vishal.l.verma@...el.com>
> > Cc: Linda Knippers <linda.knippers@....com>
> > ---
> > v2: Send notifications for the clearing case
> > ---
>
> This looks good to me, I've applied it, but I also want to extend the
> ndctl unit tests to cover this mechanism.
Right. For the time being, would you mind to use the attached test
program for your sanity tests? It simply monitors sysfs notifications
and prints badblocks info... Sorry for inconvenience.
Since I am not familiar with the ndctl unit tests and I am traveling for
the rest of the month, I may have to look into it after I am back.
Thanks!
-Toshi
View attachment "test_sysfs_notify.c" of type "text/plain" (1160 bytes)
Powered by blists - more mailing lists