linux-kernel - Re: [PATCH] libnvdimm, pmem: clarify the write+clear

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 for Android: free password hash cracker in your pocket

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

Message-ID: <x49vb3j6oj4.fsf@segfault.boston.devel.redhat.com>
Date:	Fri, 15 Apr 2016 08:32:15 -0400
From:	Jeff Moyer <jmoyer@...hat.com>
To:	Dan Williams <dan.j.williams@...el.com>
Cc:	linux-nvdimm@...1.01.org, Vishal Verma <vishal.l.verma@...el.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] libnvdimm, pmem: clarify the write+clear_poison+write flow

Dan Williams <dan.j.williams@...el.com> writes:

> The ACPI specification does not specify the state of data after a clear
> poison operation.  Potential future libnvdimm bus implementations for
> other architectures also might not specify or disagree on the state of
> data after clear poison.  Clarify why we write twice.

Thanks, Dan, looks good.

Reviewed-by: Jeff Moyer <jmoyer@...hat.com>