From: Dan Williams <dan.j.williams@intel.com>
To: Jason Gunthorpe <jgg@ziepe.ca>
Cc: Yi Zhang <yi.zhang@redhat.com>, linux-nvdimm <linux-nvdimm@lists.01.org>
Subject: Re: regression from 5.10.0-rc3: BUG: Bad page state in process kworker/41:0 pfn:891066 during fio on devdax
Date: Mon, 9 Nov 2020 09:26:19 -0800 [thread overview]
Message-ID: <CAPcyv4gJG_-gGwzaenQdnVq13JUWLjEnsTV+e4swuVtpGVpC8g@mail.gmail.com> (raw)
In-Reply-To: <20201109141216.GD244516@ziepe.ca>
On Mon, Nov 9, 2020 at 6:12 AM Jason Gunthorpe <jgg@ziepe.ca> wrote:
>
> Wow, this is surprising
>
> This has been widely backported already, Dan please check??
>
> I thought pgprot_decrypted was a NOP on most x86 platforms -
> sme_me_mask == 0:
>
> #define __sme_set(x) ((x) | sme_me_mask)
> #define __sme_clr(x) ((x) & ~sme_me_mask)
>
> ??
>
> Confused how this can be causing DAX issues
Does that correctly preserve the "soft" pte bits? Especially
PTE_DEVMAP that DAX uses?
I'll check...
_______________________________________________
Linux-nvdimm mailing list -- linux-nvdimm@lists.01.org
To unsubscribe send an email to linux-nvdimm-leave@lists.01.org
next prev parent reply other threads:[~2020-11-09 17:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1934921834.1085815.1604889035798.JavaMail.zimbra@redhat.com>
2020-11-09 2:38 ` regression from 5.10.0-rc3: BUG: Bad page state in process kworker/41:0 pfn:891066 during fio on devdax Yi Zhang
2020-11-09 3:00 ` Dan Williams
2020-11-09 3:13 ` Yi Zhang
2020-11-09 12:11 ` Yi Zhang
[not found] ` <20201109141216.GD244516@ziepe.ca>
2020-11-09 17:26 ` Dan Williams [this message]
[not found] ` <20201109175442.GE244516@ziepe.ca>
2020-11-10 0:36 ` Jason Gunthorpe
2020-11-10 7:36 ` Yi Zhang
2020-11-10 16:51 ` Yi Zhang
2020-11-11 3:44 ` Yi Zhang
2020-11-18 14:02 ` Yi Zhang
2020-12-01 1:36 ` 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=CAPcyv4gJG_-gGwzaenQdnVq13JUWLjEnsTV+e4swuVtpGVpC8g@mail.gmail.com \
--to=dan.j.williams@intel.com \
--cc=jgg@ziepe.ca \
--cc=linux-nvdimm@lists.01.org \
--cc=yi.zhang@redhat.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;
as well as URLs for NNTP newsgroup(s).