[GIT,PULL] libnvdimm fixes for v5.0-rc4
mbox series

Message ID f0086a11a40fb97503fb559b53dcc94c9f873e32.camel@intel.com
State New
Headers show
Series
  • [GIT,PULL] libnvdimm fixes for v5.0-rc4
Related show

Pull-request

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

Message

Dan Williams Jan. 26, 2019, 11:30 p.m. UTC
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(-)

Comments

Linus Torvalds Feb. 2, 2019, 7:12 p.m. UTC | #1
On Sat, Jan 26, 2019 at 3:31 PM Williams, Dan J
<dan.j.williams@intel.com> wrote:
>
> Hi Linus, please pull from:
>
>   git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm tags/libnvdimm-fixes-5.0-rc4

Hmm. One more pr-tracker-bot note: going through the pull requests
from the last week, I notice that this one didn't get a pr-tracker
response.

It looks like lkml still hates you, so your pull request email never
made it to the list despite being cc'd. And thus it never makes it to
the lore and pr-tracker-bot infrastructure either.

Have you tried looking into why lkml has that red-hot hatred of your emails?

Because it does seem to be personal - you have pissed off the email
gods some way. Did you get a bounce?

           Linus
Dan Williams Feb. 2, 2019, 8:38 p.m. UTC | #2
On Sat, Feb 2, 2019 at 11:12 AM Linus Torvalds
<torvalds@linux-foundation.org> wrote:
>
> On Sat, Jan 26, 2019 at 3:31 PM Williams, Dan J
> <dan.j.williams@intel.com> wrote:
> >
> > Hi Linus, please pull from:
> >
> >   git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm tags/libnvdimm-fixes-5.0-rc4
>
> Hmm. One more pr-tracker-bot note: going through the pull requests
> from the last week, I notice that this one didn't get a pr-tracker
> response.
>
> It looks like lkml still hates you, so your pull request email never
> made it to the list despite being cc'd. And thus it never makes it to
> the lore and pr-tracker-bot infrastructure either.
>
> Have you tried looking into why lkml has that red-hot hatred of your emails?
>
> Because it does seem to be personal - you have pissed off the email
> gods some way. Did you get a bounce?

No bounce, but I at least have good company in the shunned group.
Mel's analysis of the impact of page-allocator randomization [1]
somehow also missed lore.kernel.org, but lkml.org caught it [2]. Add
Dave Hansen on the outside chance his mail scripts have caught other
instances of patches sent to the list but not archived in
lore.kernel.org.

[1]: <20181012082213.GE5819@techsingularity.net>
[2]: https://lkml.org/lkml/2018/10/12/309