From: Dan Williams <dan.j.williams@intel.com>
To: Pasha Tatashin <pasha.tatashin@soleen.com>,
Alison Schofield <alison.schofield@intel.com>
Cc: Sourav Panda <souravpanda@google.com>, <corbet@lwn.net>,
<gregkh@linuxfoundation.org>, <rafael@kernel.org>,
<akpm@linux-foundation.org>, <mike.kravetz@oracle.com>,
<muchun.song@linux.dev>, <rppt@kernel.org>, <david@redhat.com>,
<rdunlap@infradead.org>, <chenlinxuan@uniontech.com>,
<yang.yang29@zte.com.cn>, <tomas.mudrunka@gmail.com>,
<bhelgaas@google.com>, <ivan@cloudflare.com>,
<yosryahmed@google.com>, <hannes@cmpxchg.org>,
<shakeelb@google.com>, <kirill.shutemov@linux.intel.com>,
<wangkefeng.wang@huawei.com>, <adobriyan@gmail.com>,
<vbabka@suse.cz>, <Liam.Howlett@oracle.com>, <surenb@google.com>,
<linux-kernel@vger.kernel.org>, <linux-fsdevel@vger.kernel.org>,
<linux-doc@vger.kernel.org>, <linux-mm@kvack.org>,
<willy@infradead.org>, <weixugc@google.com>,
David Rientjes <rientjes@google.com>, <nvdimm@lists.linux.dev>,
<linux-cxl@vger.kernel.org>, <yi.zhang@redhat.com>
Subject: Re: [PATCH v13] mm: report per-page metadata information
Date: Mon, 5 Aug 2024 16:06:06 -0700 [thread overview]
Message-ID: <66b15addf1a80_c144829473@dwillia2-xfh.jf.intel.com.notmuch> (raw)
In-Reply-To: <CA+CK2bAfgamzFos1M-6AtozEDwRPJzARJOmccfZ=uzKyJ7w=kQ@mail.gmail.com>
Pasha Tatashin wrote:
[..]
> Thank you for the heads up. Can you please attach a full config file,
> also was anyone able to reproduce this problem in qemu with emulated
> nvdimm?
Yes, I can reproduce the crash just by trying to reconfigure the mode of
a pmem namespace:
# ndctl create-namespace -m raw -f -e namespace0.0
...where namespace0.0 results from:
memmap=4G!4G
...passed on the kernel command line.
Kernel config here:
https://gist.github.com/djbw/143705077103d43a735c179395d4f69a
next prev parent reply other threads:[~2024-08-05 23:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-05 22:27 Sourav Panda
2024-06-11 22:30 ` Andrew Morton
2024-06-12 17:53 ` Pasha Tatashin
2024-08-02 19:02 ` Alison Schofield
2024-08-05 18:40 ` Pasha Tatashin
2024-08-05 23:06 ` Dan Williams [this message]
2024-08-05 23:18 ` 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=66b15addf1a80_c144829473@dwillia2-xfh.jf.intel.com.notmuch \
--to=dan.j.williams@intel.com \
--cc=Liam.Howlett@oracle.com \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=alison.schofield@intel.com \
--cc=bhelgaas@google.com \
--cc=chenlinxuan@uniontech.com \
--cc=corbet@lwn.net \
--cc=david@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=hannes@cmpxchg.org \
--cc=ivan@cloudflare.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@oracle.com \
--cc=muchun.song@linux.dev \
--cc=nvdimm@lists.linux.dev \
--cc=pasha.tatashin@soleen.com \
--cc=rafael@kernel.org \
--cc=rdunlap@infradead.org \
--cc=rientjes@google.com \
--cc=rppt@kernel.org \
--cc=shakeelb@google.com \
--cc=souravpanda@google.com \
--cc=surenb@google.com \
--cc=tomas.mudrunka@gmail.com \
--cc=vbabka@suse.cz \
--cc=wangkefeng.wang@huawei.com \
--cc=weixugc@google.com \
--cc=willy@infradead.org \
--cc=yang.yang29@zte.com.cn \
--cc=yi.zhang@redhat.com \
--cc=yosryahmed@google.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