From: Yi Zhang <yi.zhang@redhat.com>
To: Jason Gunthorpe <jgg@nvidia.com>,
Dan Williams <dan.j.williams@intel.com>
Cc: 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: Tue, 10 Nov 2020 15:36:04 +0800 [thread overview]
Message-ID: <27b0fccb-7f71-ca99-129d-bd3e373c2a85@redhat.com> (raw)
In-Reply-To: <20201110003616.GA525483@nvidia.com>
On 11/10/20 8:36 AM, Jason Gunthorpe wrote:
> On Mon, Nov 09, 2020 at 01:54:42PM -0400, Jason Gunthorpe wrote:
>> On Mon, Nov 09, 2020 at 09:26:19AM -0800, Dan Williams wrote:
>>> 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...
>> extern u64 sme_me_mask;
>> #define __pgprot(x) ((pgprot_t) { (x) } )
>> #define pgprot_val(x) ((x).pgprot)
>> #define __sme_clr(x) ((x) & ~sme_me_mask)
>> #define pgprot_decrypted(prot) __pgprot(__sme_clr(pgprot_val(prot)))
>>
>> static inline int io_remap_pfn_range(struct vm_area_struct *vma,
>> unsigned long addr, unsigned long pfn,
>> unsigned long size, pgprot_t prot)
>> {
>> return remap_pfn_range(vma, addr, pfn, size, pgprot_decrypted(prot));
>> }
>>
>> Not seeing how that could change the pgprot in any harmful way?
>>
>> Yi, are you using a platform where sme_me_mask != 0 ?
>>
>> That code looks clearly like it would only trigger on AMD SME systems,
>> is that what you are using?
> Can't be, the system is too old:
>
> [ 398.455914] Hardware name: HP ProLiant DL380 Gen9/ProLiant DL380 Gen9, BIOS P89 10/05/2016
>
> I'm at a total loss how this change could even do anything on a
> non-AMD system, let alone how this intersects in any way with DEVDAX,
> which I could not find being used with io_remap_pfn_range()
I will double confirm it.
> How confident are you in the bisection?
>
> Jason
>
_______________________________________________
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-10 7:36 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
[not found] ` <20201109175442.GE244516@ziepe.ca>
2020-11-10 0:36 ` Jason Gunthorpe
2020-11-10 7:36 ` Yi Zhang [this message]
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=27b0fccb-7f71-ca99-129d-bd3e373c2a85@redhat.com \
--to=yi.zhang@redhat.com \
--cc=dan.j.williams@intel.com \
--cc=jgg@nvidia.com \
--cc=linux-nvdimm@lists.01.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