From: Dave Jiang <dave.jiang@intel.com>
To: <torvalds@linux-foundation.org>
Cc: <dan.j.williams@intel.com>, <vishal.l.verma@intel.com>,
Ira Weiny <ira.weiny@intel.com>, <nvdimm@lists.linux.dev>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] NVDIMM and DAX for 6.6
Date: Wed, 30 Aug 2023 10:07:56 -0700 [thread overview]
Message-ID: <12c76f8e-aae8-2cab-4ab0-571a8c806423@intel.com> (raw)
Hi Linus, please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm.git
tags/libnvdimm-for-6.6
... to receive the libnvdimm and DAX updates for v6.6
This is mostly small cleanups, fixes, and with a change to prevent
zero-sized namespace exposed to user for nvdimm.
It has appeared in linux-next with no reported issues.
The following changes since commit fdf0eaf11452d72945af31804e2a1048ee1b574c:
Linux 6.5-rc2 (2023-07-16 15:10:37 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm.git
tags/libnvdimm-for-6.6
for you to fetch changes up to 08ca6906a4b7e48f8e93b7c1f49a742a415be6d5:
nvdimm: Fix dereference after free in register_nvdimm_pmu()
(2023-08-17 09:34:03 -0700)
----------------------------------------------------------------
nvdimm changes for v6.6 merge window
- kstrtobool() conversion for nvdimm
- Add REQ_OP_WRITE for virtio_pmem
- Header files update for of_pmem
- Restrict zero-sized namespace from being exposed to user
- Avoid unnecessary endian conversion
- Fix mem leak in nvdimm pmu
- Fix dereference after free in nvdimm pmu
----------------------------------------------------------------
Aneesh Kumar K.V (2):
nvdimm/pfn_dev: Prevent the creation of zero-sized namespaces
nvdimm/pfn_dev: Avoid unnecessary endian conversion
Christophe JAILLET (1):
nvdimm: Use kstrtobool() instead of strtobool()
Hou Tao (1):
virtio_pmem: add the missing REQ_OP_WRITE for flush bio
Konstantin Meskhidze (2):
nvdimm: Fix memleak of pmu attr_groups in unregister_nvdimm_pmu()
nvdimm: Fix dereference after free in register_nvdimm_pmu()
Rob Herring (1):
nvdimm: Explicitly include correct DT includes
drivers/nvdimm/namespace_devs.c | 3 ++-
drivers/nvdimm/nd_perf.c | 3 ++-
drivers/nvdimm/nd_virtio.c | 3 ++-
drivers/nvdimm/of_pmem.c | 4 ++--
drivers/nvdimm/pfn_devs.c | 20 +++++++++++++-------
drivers/nvdimm/pmem.c | 3 ++-
drivers/nvdimm/region_devs.c | 5 +++--
7 files changed, 26 insertions(+), 15 deletions(-)
next reply other threads:[~2023-08-30 17:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-30 17:07 Dave Jiang [this message]
2023-08-31 4:30 ` [GIT PULL] NVDIMM and DAX for 6.6 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=12c76f8e-aae8-2cab-4ab0-571a8c806423@intel.com \
--to=dave.jiang@intel.com \
--cc=dan.j.williams@intel.com \
--cc=ira.weiny@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nvdimm@lists.linux.dev \
--cc=torvalds@linux-foundation.org \
--cc=vishal.l.verma@intel.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).