All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Williams, Dan J" <dan.j.williams@intel.com>
To: "torvalds@linux-foundation.org" <torvalds@linux-foundation.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>
Subject: [GIT PULL] libnvdimm fixes for v5.0-rc4
Date: Sat, 26 Jan 2019 23:30:58 +0000	[thread overview]
Message-ID: <f0086a11a40fb97503fb559b53dcc94c9f873e32.camel@intel.com> (raw)

Hi Linus, please pull from:

  git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm tags/libnvdimm-fixes-5.0-rc4

...to receive a fix for namespace label support for non-Intel NVDIMMs
that implement the ACPI standard label method. This has apparently
never worked and could wait for v5.1. However it has enough visibility
with hardware vendors [1] and distro bug trackers [2], and low enough
risk that I decided it should go in for -rc4. The other fixups target
the new, for v5.0, nvdimm security functionality. The larger init path
fixup closes a memory leak and a potential userspace lockup due to
missed notifications.

These have all soaked in -next for a week with no reported issues.

[1]: https://github.com/pmem/ndctl/issues/78
[2]: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811785

---

The following changes since commit 49a57857aeea06ca831043acbb0fa5e0f50602fd:

  Linux 5.0-rc3 (2019-01-21 13:14:44 +1300)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm tags/libnvdimm-fixes-5.0-rc4

for you to fetch changes up to 11189c1089da413aa4b5fd6be4c4d47c78968819:

  acpi/nfit: Fix command-supported detection (2019-01-21 09:58:31 -0800)

----------------------------------------------------------------
libnvdimm v5.0-rc4

* Fix support for NVDIMMs that implement the ACPI standard label
  methods.
* Fix error handling for security overwrite (memory leak / userspace
  hang condition), and another one-line security cleanup

----------------------------------------------------------------
Dan Williams (3):
      libnvdimm/security: Require nvdimm_security_setup_events() to succeed
      acpi/nfit: Block function zero DSMs
      acpi/nfit: Fix command-supported detection

Dave Jiang (1):
      nfit_test: fix security state pull for nvdimm security nfit_test

 drivers/acpi/nfit/core.c         | 66 ++++++++++++++++++++++++++++------------
 drivers/nvdimm/dimm.c            |  6 ++++
 drivers/nvdimm/dimm_devs.c       | 22 +++++++++++---
 drivers/nvdimm/nd.h              |  1 +
 include/linux/libnvdimm.h        |  1 -
 tools/testing/nvdimm/dimm_devs.c |  4 +--
 6 files changed, 73 insertions(+), 27 deletions(-)
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm

             reply	other threads:[~2019-01-26 23:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-26 23:30 Williams, Dan J [this message]
2019-02-02 19:12 ` [GIT PULL] libnvdimm fixes for v5.0-rc4 Linus Torvalds
2019-02-02 19:12   ` Linus Torvalds
2019-02-02 20:38   ` Dan Williams
2019-02-02 20:38     ` 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=f0086a11a40fb97503fb559b53dcc94c9f873e32.camel@intel.com \
    --to=dan.j.williams@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvdimm@lists.01.org \
    --cc=torvalds@linux-foundation.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.