From: Andrew Morton <akpm@linux-foundation.org>
To: Muchun Song <muchun.song@linux.dev>
Cc: Muchun Song <songmuchun@bytedance.com>,
Dan Williams <djbw@kernel.org>,
Vishal Verma <vishal.l.verma@intel.com>,
Dave Jiang <dave.jiang@intel.com>,
Alison Schofield <alison.schofield@intel.com>,
Joao Martins <joao.m.martins@oracle.com>,
nvdimm@lists.linux.dev, linux-cxl@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
"Ritesh Harjani (IBM)" <ritesh.list@gmail.com>
Subject: Re: [PATCH v5] dax/bus: Fix Device DAX range alignment validation
Date: Sat, 24 Oct 2026 19:59:11 -0700 [thread overview]
Message-ID: <20261024195911.64e9d7fbb7522bab8193911d@linux-foundation.org> (raw)
In-Reply-To: <5AFA3B1F-48C6-49FF-A6FF-7D71153671CF@linux.dev>
On Sun, 25 Oct 2026 10:52:29 +0800 Muchun Song <muchun.song@linux.dev> wrote:
> > your series "mm: Unify device DAX and HugeTLB vmemmap population paths"
> > exposes it. That's
> >
> > 4b77739fe789 ("mm/sparse-vmemmap: drop VMEMMAP_POPULATE_DAX").
> >
> > I intend to send this to Linus next week.
> >
> > Maybe also a Fixes: 4b77739fe789. That series didn't create the bug,
> > but this data provides notification to people who are backporting this
> > series (unlikely) "hey, you need to add this fix as well".
>
> Based on the above info, do you think it is necessary to include this
> commit as a Fixes tag? My inclination is to exclude it, because the
> issue is still there. It's just that it gets triggered earlier when the
> debug kernel is enabled.
OK, skip that. This patch "dax/bus: Fix Device DAX range alignment
validation v5" has cc:stable anyway so things will work out.
prev parent reply other threads:[~2026-10-25 2:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-24 11:25 Muchun Song
2026-10-25 1:38 ` Andrew Morton
2026-10-25 2:10 ` Ritesh Harjani
2026-10-25 2:52 ` Muchun Song
2026-10-25 2:59 ` Andrew Morton [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=20261024195911.64e9d7fbb7522bab8193911d@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=alison.schofield@intel.com \
--cc=dave.jiang@intel.com \
--cc=djbw@kernel.org \
--cc=joao.m.martins@oracle.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=muchun.song@linux.dev \
--cc=nvdimm@lists.linux.dev \
--cc=ritesh.list@gmail.com \
--cc=songmuchun@bytedance.com \
--cc=stable@vger.kernel.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
all inboxes | Powered by JetHome®