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 4.9-rc7
Date: Sat, 26 Nov 2016 17:27:25 +0000	[thread overview]
Message-ID: <1480181243.3767.8.camel@intel.com> (raw)

Hi Linus, please pull from:

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

...to receive:

* Fix a crash that occurs at driver initialization if the memory region
is already busy (request_mem_region() fails).

* Fix a vma validation check that mistakenly allows a private device-
dax mapping to be established.  Device-dax explicitly forbids private
mappings so it can guarantee a given fault granularity and backing
memory type.

Both of these fixes have soaked in -next and are tagged for -stable.

---

The following changes since commit ed99d3673e082b78b20208f346d2cd375483a779:

  Merge branch 'libnvdimm-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm (2016-10-28 11:47:45 -0700)

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 4cb19355ea19995941ccaad115dbfac6b75215ca:

  device-dax: fail all private mapping attempts (2016-11-16 09:00:38 -0800)

----------------------------------------------------------------
Dan Williams (2):
      device-dax: check devm_nsio_enable() return value
      device-dax: fail all private mapping attempts

 drivers/dax/dax.c  | 4 ++--
 drivers/dax/pmem.c | 4 +++-
 2 files changed, 5 insertions(+), 3 deletions(-)
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm

WARNING: multiple messages have this Message-ID (diff)
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@ml01.01.org>
Subject: [GIT PULL] libnvdimm fixes for 4.9-rc7
Date: Sat, 26 Nov 2016 17:27:25 +0000	[thread overview]
Message-ID: <1480181243.3767.8.camel@intel.com> (raw)

Hi Linus, please pull from:

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

...to receive:

* Fix a crash that occurs at driver initialization if the memory region
is already busy (request_mem_region() fails).

* Fix a vma validation check that mistakenly allows a private device-
dax mapping to be established.  Device-dax explicitly forbids private
mappings so it can guarantee a given fault granularity and backing
memory type.

Both of these fixes have soaked in -next and are tagged for -stable.

---

The following changes since commit ed99d3673e082b78b20208f346d2cd375483a779:

  Merge branch 'libnvdimm-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm (2016-10-28 11:47:45 -0700)

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 4cb19355ea19995941ccaad115dbfac6b75215ca:

  device-dax: fail all private mapping attempts (2016-11-16 09:00:38 -0800)

----------------------------------------------------------------
Dan Williams (2):
      device-dax: check devm_nsio_enable() return value
      device-dax: fail all private mapping attempts

 drivers/dax/dax.c  | 4 ++--
 drivers/dax/pmem.c | 4 +++-
 2 files changed, 5 insertions(+), 3 deletions(-)

             reply	other threads:[~2016-11-26 17:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-26 17:27 Williams, Dan J [this message]
2016-11-26 17:27 ` [GIT PULL] libnvdimm fixes for 4.9-rc7 Williams, Dan J

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=1480181243.3767.8.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.