From: "Verma, Vishal L" <vishal.l.verma@intel.com>
To: "Williams, Dan J" <dan.j.williams@intel.com>
Cc: "linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>
Subject: Re: [PATCH] test: regression test for a kernel panic on running ARS for BTTs
Date: Thu, 27 Apr 2017 23:14:13 +0000 [thread overview]
Message-ID: <1493334771.30844.6.camel@intel.com> (raw)
In-Reply-To: <CAPcyv4jPD1vvtdnw1-eaTNz_PfPQwutFAd3kBCqB2XsptT3TFw@mail.gmail.com>
On Thu, 2017-04-27 at 16:06 -0700, Dan Williams wrote:
> On Thu, Apr 27, 2017 at 3:39 PM, Vishal Verma <vishal.l.verma@intel.co
> m> wrote:
> > Runing an Address Range Scrub on a region with a BTT namespace would
> > cause a kernel null pointer dereference. This tests we don't regress
> > that.
> >
> > Cc: Toshi Kani <toshi.kani@hpe.com>
> > Cc: Dan Williams <dan.j.williams@intel.com>
> > Signed-off-by: Vishal Verma <vishal.l.verma@intel.com>
> > ---
> > test/Makefile.am | 3 +-
> > test/btt-ars-panic.sh | 93
> > +++++++++++++++++++++++++++++++++++++++++++++++++++
> > 2 files changed, 95 insertions(+), 1 deletion(-)
> > create mode 100755 test/btt-ars-panic.sh
> >
[..]
> > +test_pass()
> > +{
> > + # If the test failed, there would have been a kernel null
> > pointer
> > + # dereference, and a subsequent ndctl disable-region would
> > hang
> > + $ndctl disable-region all &
>
> Test looks good. This line makes me think we need something like
> "ndctl wait-scrub-bus".
Yes, perhaps also something to start a scrub..
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
prev parent reply other threads:[~2017-04-27 23:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-27 22:39 [PATCH] test: regression test for a kernel panic on running ARS for BTTs Vishal Verma
2017-04-27 23:06 ` Dan Williams
2017-04-27 23:14 ` Verma, Vishal L [this message]
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=1493334771.30844.6.camel@intel.com \
--to=vishal.l.verma@intel.com \
--cc=dan.j.williams@intel.com \
--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.