mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dan Williams <dan.j.williams@intel.com>
To: <torvalds@linux-foundation.org>
Cc: <nvdimm@lists.linux.dev>, <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] NVDIMM and DAX fixes for 6.2-final
Date: Fri, 10 Feb 2023 18:31:55 -0800	[thread overview]
Message-ID: <63e6fe1b27ea3_88e129491@dwillia2-mobl3.amr.corp.intel.com.notmuch> (raw)

Hi Linus, please pull from:

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

...to receive a fix for an issue that could causes users to
inadvertantly reserve too much capacity when debugging the KMSAN and
persistent memory namespace, a lockdep fix, and a kernel-doc build
warning.

This has all appeared in -next with no reported issues.

---


The following changes since commit 88603b6dc419445847923fcb7fe5080067a30f98:

  Linux 6.2-rc2 (2023-01-01 13:53:16 -0800)

are available in the Git repository at:

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

for you to fetch changes up to c91d713630848460de8669e6570307b7e559863b:

  nvdimm: Support sizeof(struct page) > MAX_STRUCT_PAGE_SIZE (2023-01-28 15:32:36 -0800)

----------------------------------------------------------------
libnvdimm fixes for 6.2

- Resolve the conflict between KMSAN and NVDIMM with respect to
  reserving pmem namespace / volume capacity for larger
  sizeof(struct page)

- Fix a lockdep warning in the the NFIT code

- Fix a kernel-doc build warning

----------------------------------------------------------------
Dan Williams (1):
      nvdimm: Support sizeof(struct page) > MAX_STRUCT_PAGE_SIZE

Randy Dunlap (1):
      dax: super.c: fix kernel-doc bad line warning

Vishal Verma (1):
      ACPI: NFIT: fix a potential deadlock during NFIT teardown

 drivers/acpi/nfit/core.c  |  2 +-
 drivers/dax/super.c       |  2 +-
 drivers/nvdimm/Kconfig    | 19 +++++++++++++++++++
 drivers/nvdimm/nd.h       |  2 +-
 drivers/nvdimm/pfn_devs.c | 42 +++++++++++++++++++++++++++---------------
 5 files changed, 49 insertions(+), 18 deletions(-)


             reply	other threads:[~2023-02-11  2:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-11  2:31 Dan Williams [this message]
2023-02-11 19:11 ` pr-tracker-bot

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=63e6fe1b27ea3_88e129491@dwillia2-mobl3.amr.corp.intel.com.notmuch \
    --to=dan.j.williams@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nvdimm@lists.linux.dev \
    --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

all inboxes | Powered by JetHome®