linux-kernel - Re: [PATCH 5/5] dax: "Hotplug" persistent memory for use like normal RAM

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:   Mon, 11 Feb 2019 08:22:20 -0800
From:   Dave Hansen <dave.hansen@...el.com>
To:     Brice Goglin <Brice.Goglin@...ia.fr>,
        Dave Hansen <dave.hansen@...ux.intel.com>,
        linux-kernel@...r.kernel.org
Cc:     thomas.lendacky@....com, mhocko@...e.com,
        linux-nvdimm@...ts.01.org, tiwai@...e.de, ying.huang@...el.com,
        linux-mm@...ck.org, jglisse@...hat.com, bp@...e.de,
        baiyaowei@...s.chinamobile.com, zwisler@...nel.org,
        bhelgaas@...gle.com, fengguang.wu@...el.com,
        akpm@...ux-foundation.org
Subject: Re: [PATCH 5/5] dax: "Hotplug" persistent memory for use like normal
 RAM

On 2/9/19 3:00 AM, Brice Goglin wrote:
> I've used your patches on fake hardware (memmap=xx!yy) with an older
> nvdimm-pending branch (without Keith's patches). It worked fine. This
> time I am running on real Intel hardware. Any idea where to look ?

I've run them on real Intel hardware too.

Could you share the exact sequence of commands you're issuing to
reproduce the hang?  My guess would be that there's some odd interaction
between Dan's latest branch and my now (slightly) stale patches.

I'll refresh them this week and see if I can reproduce what you're seeing.