From: Alison Schofield <alison.schofield@intel.com>
To: John Groves <john@jagalactic.com>
Cc: John Groves <John@groves.net>, Dan Williams <djbw@kernel.org>,
John Groves <jgroves@micron.com>,
Vishal Verma <vishal.l.verma@intel.com>,
Dave Jiang <dave.jiang@intel.com>,
Matthew Wilcox <willy@infradead.org>, Jan Kara <jack@suse.cz>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>,
Miklos Szeredi <miklos@szeredi.hu>, Ira Weiny <iweiny@kernel.org>,
Jonathan Cameron <jic23@kernel.org>,
"nvdimm@lists.linux.dev" <nvdimm@lists.linux.dev>,
"linux-cxl@vger.kernel.org" <linux-cxl@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH V6 0/10] Fixes to the previously-merged drivers/dax/fsdev series
Date: Tue, 14 Jul 2026 17:06:33 -0700 [thread overview]
Message-ID: <albPCdtgNi6sDIsJ@aschofie-mobl2.lan> (raw)
In-Reply-To: <0100019ecc080a68-8dc0c99f-ab17-4aa9-83d9-490e9c97ac2e-000000@email.amazonses.com>
On Mon, Jun 15, 2026 at 04:05:39PM +0000, John Groves wrote:
> From: John Groves <john@groves.net>
>
> This series applies bug fixes (mostly found via sashiko) to the dax/fsdev
> series. It has been soaking in the famfs CI pipeline and 1) won't affect
> anything that doesn't use drivers/dax/fsdev.c, and 2) doesn't affect any
> known workloads -- although the bugs would have manifested when multi-range
> DCD dax devices are a thing (soon-ish).
>
> Most of the series is confined to drivers/dax/fsdev.c. Two patches touch
> shared DAX core in drivers/dax/super.c: patch 8 reads holder_ops once in
> dax_holder_notify_failure() to close a double-fetch NULL dereference, and
> patch 9 reorders fs_put_dax() and adds a WARN_ON(). fs_put_dax() is used by
> ext2/ext4/erofs/xfs, but only holder-passing callers (like XFS in-tree) will
> see a behavior change, and only a new warning if they misuse it.
Series applied to libnvdimm-for-next:
https://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm.git/
prev parent reply other threads:[~2026-07-15 0:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260615160531.17432-1-john@jagalactic.com>
2026-06-15 16:05 ` John Groves
[not found] ` <20260615160616.17456-1-john@jagalactic.com>
2026-06-15 16:06 ` [PATCH V6 01/10] dax: fix misleading comment about share/index union in dax_folio_reset_order() John Groves
[not found] ` <20260615160626.17473-1-john@jagalactic.com>
2026-06-15 16:06 ` [PATCH V6 02/10] dax/fsdev: fix multi-range offset in memory_failure handler John Groves
2026-06-23 6:55 ` Richard Cheng
[not found] ` <20260615160634.17496-1-john@jagalactic.com>
2026-06-15 16:06 ` [PATCH V6 03/10] dax/fsdev: clear vmemmap_shift when binding static pgmap John Groves
[not found] ` <20260615160648.17513-1-john@jagalactic.com>
2026-06-15 16:06 ` [PATCH V6 04/10] dax/fsdev: don't leave a dangling dev_dax->pgmap on probe failure John Groves
[not found] ` <20260615160656.17533-1-john@jagalactic.com>
2026-06-15 16:07 ` [PATCH V6 05/10] dax/fsdev: clear pgmap ops and owner on unbind John Groves
2026-06-22 10:31 ` Richard Cheng
[not found] ` <20260615160704.17550-1-john@jagalactic.com>
2026-06-15 16:07 ` [PATCH V6 06/10] dax/fsdev: use __va(phys) for kaddr in direct_access John Groves
[not found] ` <20260615160713.17567-1-john@jagalactic.com>
2026-06-15 16:07 ` [PATCH V6 07/10] dax/fsdev: fail probe on invalid pgmap offset John Groves
[not found] ` <20260615160724.17584-1-john@jagalactic.com>
2026-06-15 16:07 ` [PATCH V6 08/10] dax: read holder_ops once in dax_holder_notify_failure() John Groves
[not found] ` <20260615160733.17601-1-john@jagalactic.com>
2026-06-15 16:07 ` [PATCH V6 09/10] dax: fix holder_ops race in fs_put_dax() John Groves
[not found] ` <20260615160741.17618-1-john@jagalactic.com>
2026-06-15 16:07 ` [PATCH V6 10/10] dax: fsdev.c minor formatting cleanup John Groves
2026-07-15 0:06 ` Alison Schofield [this message]
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=albPCdtgNi6sDIsJ@aschofie-mobl2.lan \
--to=alison.schofield@intel.com \
--cc=John@groves.net \
--cc=brauner@kernel.org \
--cc=dave.jiang@intel.com \
--cc=djbw@kernel.org \
--cc=iweiny@kernel.org \
--cc=jack@suse.cz \
--cc=jgroves@micron.com \
--cc=jic23@kernel.org \
--cc=john@jagalactic.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=nvdimm@lists.linux.dev \
--cc=viro@zeniv.linux.org.uk \
--cc=vishal.l.verma@intel.com \
--cc=willy@infradead.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