All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Williams <dan.j.williams@intel.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux NVDIMM <nvdimm@lists.linux.dev>,
	 Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] libnvdimm / persistent memory update for v5.15
Date: Wed, 8 Sep 2021 16:18:28 -0700	[thread overview]
Message-ID: <CAPcyv4hvzS1c01BweBkgDsjg=VGnaUUKi7b6j+1X=Rqzzm961Q@mail.gmail.com> (raw)

Hi Linus, please pull from:

  git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm
tags/libnvdimm-for-5.15

...to receive the libnvdimm update for v5.15. It includes a bug fix
for a long standing race in the driver shutdown path. More people are
stress testing the nvdimm configuration mechanism which is a welcome
sign. There is also a rework of the infrastructure for looking up the
dax_device associated with a block_device.

This collided (silent conflict) with the erofs updates to add dax
support this cycle. Gao Xiang noted this as well in the erofs pull
request. Stephen's fix [1] looked correct to me. Otherwise, it has
been in -next for a while with no other reported issues.

Please pull, thanks,
Dan

[1]: https://lore.kernel.org/r/20210830170938.6fd8813d@canb.auug.org.au

---


The following changes since commit e22ce8eb631bdc47a4a4ea7ecf4e4ba499db4f93:

  Linux 5.14-rc7 (2021-08-22 14:24:56 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm
tags/libnvdimm-for-5.15

for you to fetch changes up to 3fc3725357414636d91be1558ce8b14f228b4bda:

  Merge branch 'for-5.15/fsdax-cleanups' into for-5.15/libnvdimm
(2021-09-08 15:58:13 -0700)

----------------------------------------------------------------
libnvdimm for v5.15

- Fix a race condition in the teardown path of raw mode pmem namespaces.

- Cleanup the code that filesystems use to detect filesystem-dax
  capabilities of their underlying block device.

----------------------------------------------------------------
Christoph Hellwig (9):
      fsdax: improve the FS_DAX Kconfig description and help text
      dax: stop using bdevname
      dm: use fs_dax_get_by_bdev instead of dax_get_by_host
      dax: mark dax_get_by_host static
      dax: move the dax_read_lock() locking into dax_supported
      dax: remove __generic_fsdax_supported
      dax: stub out dax_supported for !CONFIG_FS_DAX
      xfs: factor out a xfs_buftarg_is_dax helper
      dax: remove bdev_dax_supported

Dan Williams (1):
      Merge branch 'for-5.15/fsdax-cleanups' into for-5.15/libnvdimm

sumiyawang (1):
      libnvdimm/pmem: Fix crash triggered when I/O in-flight during unbind

 drivers/dax/super.c   | 191 +++++++++++++++++++-------------------------------
 drivers/md/dm-table.c |   9 +--
 drivers/md/dm.c       |   2 +-
 drivers/nvdimm/pmem.c |   4 +-
 fs/Kconfig            |  21 +++++-
 fs/ext2/super.c       |   3 +-
 fs/ext4/super.c       |   3 +-
 fs/xfs/xfs_super.c    |  16 +++--
 include/linux/dax.h   |  41 ++---------
 9 files changed, 119 insertions(+), 171 deletions(-)

             reply	other threads:[~2021-09-08 23:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-08 23:18 Dan Williams [this message]
2021-09-08 23:18 ` [GIT PULL] libnvdimm / persistent memory update for v5.15 Dan Williams
2021-09-09 18:55 ` 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='CAPcyv4hvzS1c01BweBkgDsjg=VGnaUUKi7b6j+1X=Rqzzm961Q@mail.gmail.com' \
    --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 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.