From: Christoph Hellwig <hch@lst.de>
To: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
Cc: "Juergen Gross" <jgross@suse.com>,
"Sagi Grimberg" <sagi@grimberg.me>,
linux-nvme@lists.infradead.org, "Jens Axboe" <axboe@fb.com>,
"Keith Busch" <kbusch@kernel.org>,
xen-devel <xen-devel@lists.xenproject.org>,
"Christoph Hellwig" <hch@lst.de>,
"Roger Pau Monné" <roger.pau@citrix.com>
Subject: Re: GPF on 0xdead000000000100 in nvme_map_data - Linux 5.9.9
Date: Fri, 4 Dec 2020 13:08:03 +0100 [thread overview]
Message-ID: <20201204120803.GA20727@lst.de> (raw)
In-Reply-To: <20201204110847.GU201140@mail-itl>
On Fri, Dec 04, 2020 at 12:08:47PM +0100, Marek Marczykowski-Górecki wrote:
> culprit:
>
> commit 9e2369c06c8a181478039258a4598c1ddd2cadfa
> Author: Roger Pau Monne <roger.pau@citrix.com>
> Date: Tue Sep 1 10:33:26 2020 +0200
>
> xen: add helpers to allocate unpopulated memory
>
> I'm adding relevant people and xen-devel to the thread.
> For completeness, here is the original crash message:
That commit definitively adds a new ZONE_DEVICE user, so it does look
related. But you are not running on Xen, are you?
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2020-12-04 12:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-29 3:56 GPF on 0xdead000000000100 in nvme_map_data - Linux 5.9.9 Marek Marczykowski-Górecki
2020-11-30 16:40 ` Keith Busch
2020-12-02 0:06 ` Marek Marczykowski-Górecki
2020-12-04 11:08 ` Marek Marczykowski-Górecki
2020-12-04 12:08 ` Christoph Hellwig [this message]
2020-12-04 12:20 ` Marek Marczykowski-Górecki
2020-12-05 8:28 ` Roger Pau Monné
2020-12-06 16:47 ` Jason Andryuk
2020-12-07 8:53 ` Jürgen Groß
2020-12-07 9:02 ` Jürgen Groß
2020-12-07 10:55 ` Jürgen Groß
2020-12-07 11:48 ` Marek Marczykowski-Górecki
2020-12-07 12:00 ` Jürgen Groß
2020-12-07 13:00 ` Marek Marczykowski-Górecki
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=20201204120803.GA20727@lst.de \
--to=hch@lst.de \
--cc=axboe@fb.com \
--cc=jgross@suse.com \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=marmarek@invisiblethingslab.com \
--cc=roger.pau@citrix.com \
--cc=sagi@grimberg.me \
--cc=xen-devel@lists.xenproject.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;
as well as URLs for NNTP newsgroup(s).