[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200717092507.GE10769@hirez.programming.kicks-ass.net>
Date: Fri, 17 Jul 2020 11:25:07 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: ira.weiny@...el.com
Cc: Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
Andy Lutomirski <luto@...nel.org>, x86@...nel.org,
Dave Hansen <dave.hansen@...ux.intel.com>,
Dan Williams <dan.j.williams@...el.com>,
Vishal Verma <vishal.l.verma@...el.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Fenghua Yu <fenghua.yu@...el.com>, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-nvdimm@...ts.01.org,
linux-fsdevel@...r.kernel.org, linux-mm@...ck.org,
linux-kselftest@...r.kernel.org
Subject: Re: [PATCH RFC V2 16/17] [dax|pmem]: Enable stray write protection
On Fri, Jul 17, 2020 at 12:20:55AM -0700, ira.weiny@...el.com wrote:
> From: Ira Weiny <ira.weiny@...el.com>
>
> Protecting against stray writes is particularly important for PMEM
> because, unlike writes to anonymous memory, writes to PMEM persists
> across a reboot. Thus data corruption could result in permanent loss of
> data. Therefore, there is no option presented to the user.
>
> Enable stray write protection by setting the flag in pgmap which
> requests it. Note if Zone Device Access Protection not be supported
> this flag will have no affect.
The actual implementation is stray-access-protection, as noted ealier.
This inconsisteny is throughout.
Powered by blists - more mailing lists