From: John Groves <John@groves.net>
To: John Groves <john@jagalactic.com>
Cc: 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>,
Alison Schofield <alison.schofield@intel.com>,
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 0/6] Fixes to the previously-merged drivers/dax/fsdev series
Date: Tue, 19 May 2026 07:19:08 -0500 [thread overview]
Message-ID: <agxU6hGczRT2DSFD@groves.net> (raw)
In-Reply-To: <0100019e3d03bba9-d27282f3-5552-4fa0-8326-981e4c13dace-000000@email.amazonses.com>
On 26/05/18 09:35PM, John Groves wrote:
> From: John Groves <john@groves.net>
>
> This series applies bug fixes (mostly found via sashiko) to the dax/fsdev
> series. This has been soaking in the famfs CI pipeline for 2+ weeks 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).
Quick note: I just noticed that this series generates a conflict on
7.1-rc4. I'll update within a day or so to clean that up.
John
next prev parent reply other threads:[~2026-05-19 12:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260518213452.31205-1-john@jagalactic.com>
2026-05-18 21:35 ` [PATCH 0/6] Fixes to the previously-merged drivers/dax/fsdev series John Groves
2026-05-18 21:35 ` [PATCH 1/6] dax: fix misleading comment about share/index union in dax_folio_reset_order() John Groves
2026-05-19 11:34 ` Jonathan Cameron
2026-05-19 12:17 ` John Groves
2026-05-18 21:36 ` [PATCH 2/6] dax/fsdev: fix multi-range offset, vmemmap_shift leak, and probe error cleanup John Groves
2026-05-18 21:36 ` [PATCH 3/6] dax/fsdev: fix kaddr for multi-range and fail probe on invalid pgmap offset John Groves
2026-05-18 21:36 ` [PATCH 4/6] dax/fsdev: clamp direct_access return to current physical range John Groves
2026-05-18 21:36 ` [PATCH 5/6] dax: fix holder_ops race in fs_put_dax() John Groves
2026-05-18 21:36 ` [PATCH 6/6] dax: replace exported dax_dev_get() with non-allocating dax_dev_find() John Groves
2026-05-19 12:19 ` John Groves [this message]
2026-05-22 3:30 ` [PATCH 0/6] Fixes to the previously-merged drivers/dax/fsdev series Alison Schofield
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=agxU6hGczRT2DSFD@groves.net \
--to=john@groves.net \
--cc=alison.schofield@intel.com \
--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