From: Dan Williams <dan.j.williams@intel.com>
To: linux-nvdimm@lists.01.org
Cc: stable@vger.kernel.org, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/5] libnvdimm: fix locked status detection
Date: Tue, 10 Apr 2018 15:39:09 -0700 [thread overview]
Message-ID: <152339994885.16061.1760220735664848631.stgit@dwillia2-desk3.amr.corp.intel.com> (raw)
The new ACPI _LSx methods moved the 'dimm locked' error status from the
result of ND_CMD_GET_CONFIG_SIZE to an error status result of
ND_CMD_GET_CONFIG_DATA. Error code translation prevents the proper error
code from making it back to the 'nd_dimm' driver.
Fix the error code propagation and add some unit test infrastructure for
regression testing this case.
---
Dan Williams (5):
libnvdimm, dimm: handle EACCES failures from label reads
tools/testing/nvdimm: allow custom error code injection
tools/testing/nvdimm: support nfit_test_dimm attributes under nfit_test.1
tools/testing/nvdimm: fix missing newline in nfit_test_dimm 'handle' attribute
tools/testing/nvdimm: enable labels for nfit_test.1 dimms
drivers/nvdimm/dimm_devs.c | 22 +++++-----
tools/testing/nvdimm/test/nfit.c | 84 +++++++++++++++++++++++++++++---------
2 files changed, 77 insertions(+), 29 deletions(-)
next reply other threads:[~2018-04-10 22:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-10 22:39 Dan Williams [this message]
2018-04-10 22:39 ` [PATCH 1/5] libnvdimm, dimm: handle EACCES failures from label reads Dan Williams
2018-04-10 22:39 ` [PATCH 2/5] tools/testing/nvdimm: allow custom error code injection Dan Williams
2018-04-10 22:39 ` [PATCH 3/5] tools/testing/nvdimm: support nfit_test_dimm attributes under nfit_test.1 Dan Williams
2018-04-10 22:39 ` [PATCH 4/5] tools/testing/nvdimm: fix missing newline in nfit_test_dimm 'handle' attribute Dan Williams
2018-04-10 22:39 ` [PATCH 5/5] tools/testing/nvdimm: enable labels for nfit_test.1 dimms Dan Williams
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=152339994885.16061.1760220735664848631.stgit@dwillia2-desk3.amr.corp.intel.com \
--to=dan.j.williams@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@lists.01.org \
--cc=stable@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).