From: Christoph Hellwig <hch@infradead.org>
To: Dan Williams <dan.j.williams@intel.com>
Cc: David Hildenbrand <david@redhat.com>,
Alison Schofield <alison.schofield@intel.com>,
Alistair Popple <apopple@nvidia.com>,
linux-mm@kvack.org, nvdimm@lists.linux.dev
Subject: Re: [BUG Report] 6.15-rc1 RIP: 0010:__lruvec_stat_mod_folio+0x7e/0x250
Date: Thu, 10 Apr 2025 01:48:25 -0700 [thread overview]
Message-ID: <Z_eF2YOaidw6OmVZ@infradead.org> (raw)
In-Reply-To: <67f6e97a4dc0b_72052944@dwillia2-xfh.jf.intel.com.notmuch>
On Wed, Apr 09, 2025 at 02:41:14PM -0700, Dan Williams wrote:
> The p2p-dma use case does not map into userspace, and the device-dax
> case has static folio order for all potential folios. So I think this
> fix is only needed for fsdax.
p2pdma pages can be mapped to userspace. Or do you mean something else?
next prev parent reply other threads:[~2025-04-10 8:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-09 0:20 [BUG Report] 6.15-rc1 RIP: 0010:__lruvec_stat_mod_folio+0x7e/0x250 Alison Schofield
2025-04-09 8:40 ` David Hildenbrand
2025-04-09 8:55 ` David Hildenbrand
2025-04-09 20:08 ` Dan Williams
2025-04-09 20:25 ` David Hildenbrand
2025-04-09 21:13 ` Alison Schofield
2025-04-09 21:41 ` Dan Williams
2025-04-10 8:48 ` Christoph Hellwig [this message]
2025-04-09 19:03 ` Dan Williams
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=Z_eF2YOaidw6OmVZ@infradead.org \
--to=hch@infradead.org \
--cc=alison.schofield@intel.com \
--cc=apopple@nvidia.com \
--cc=dan.j.williams@intel.com \
--cc=david@redhat.com \
--cc=linux-mm@kvack.org \
--cc=nvdimm@lists.linux.dev \
/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 NNTP newsgroup(s).