nvdimm.lists.linux.dev archive mirror
 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-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
	"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 4.16-rc7
Date: Fri, 23 Mar 2018 00:34:10 +0000	[thread overview]
Message-ID: <1521765242.9257.19.camel@intel.com> (raw)

Hi Linus, please pull from:

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

...to receive 2 regression fixes, 2 bug fixes for older issues, 2
fixes for new functionality added this cycle that have userspace ABI
concerns, and a small cleanup. These have appeared in a linux-next
release and have a build success report from the 0day robot.

* The 4.16 rework of altmap handling led to some configurations leaking
page table allocations due to freeing from the altmap reservation
rather than the page allocator. The impact without the fix is leaked
memory and a WARN() message when tearing down libnvdimm namespaces. The
rework also missed a place where error handling code needed to be
removed that can lead to a crash if devm_memremap_pages() fails.

* acpi_map_pxm_to_node() had a latent bug whereby it could misidentify
the closest online node to a given proximity domain.

* Block integrity handling was reworked several kernels back to allow
calling add_disk() after setting up the integrity profile. The nd_btt
and nd_blk drivers are just now catching up to fix automatic partition
detection at driver load time.

* The new peristence_domain attribute, a platform indicator of whether
cpu caches are powerfail protected for example, is meant to be a single
value enum and not a set of flags. This oversight was caught while
reviewing new userspace code in libndctl to communicate the attribute.
Fix this new enabling up so that we are not stuck with an unwanted
userspace ABI.

The following changes since commit 661e50bc853209e41a5c14a290ca4decc43cbfd1:

  Linux 4.16-rc4 (2018-03-04 14:54:11 -0800)

are available in the git repository at:

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

for you to fetch changes up to fe9a552e715dfe5167d52deb74ea16335896bdaf:

  libnvdimm, nfit: fix persistence domain reporting (2018-03-21 15:12:07 -0700)

----------------------------------------------------------------
Colin Ian King (1):
      libnvdimm: remove redundant assignment to pointer 'dev'

Dan Williams (4):
      x86, memremap: fix altmap accounting at free
      acpi, numa: fix pxm to online numa node associations
      libnvdimm, region: hide persistence_domain when unknown
      libnvdimm, nfit: fix persistence domain reporting

Oliver O'Halloran (1):
      kernel/memremap: Remove stale devres_free() call

Vishal Verma (1):
      libnvdimm, {btt, blk}: do integrity setup before add_disk()

 arch/x86/mm/init_64.c        | 60 +++++++++++++++++++++-----------------------
 drivers/acpi/nfit/core.c     | 10 +++++---
 drivers/acpi/numa.c          | 10 +++++---
 drivers/nvdimm/blk.c         |  3 +--
 drivers/nvdimm/btt.c         |  3 +--
 drivers/nvdimm/pfn_devs.c    |  2 +-
 drivers/nvdimm/region_devs.c | 17 ++++++++++---
 kernel/memremap.c            |  1 -
 8 files changed, 57 insertions(+), 49 deletions(-)
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm

                 reply	other threads:[~2018-03-23  0:27 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1521765242.9257.19.camel@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=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 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).