linux-kernel - Re: [PATCH v6 11/21] libnvdimm, nfit: add interleave-set state-tracking infrastructure

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: <1495615.0cZhPQCH7Y@vostro.rjw.lan>
Date:	Thu, 18 Jun 2015 00:06:39 +0200
From:	"Rafael J. Wysocki" <rjw@...ysocki.net>
To:	Dan Williams <dan.j.williams@...el.com>
Cc:	linux-nvdimm@...ts.01.org, mingo@...nel.org, sfr@...b.auug.org.au,
	rafael@...nel.org, neilb@...e.de, gregkh@...uxfoundation.org,
	"Rafael J. Wysocki" <rafael.j.wysocki@...el.com>,
	Robert Moore <robert.moore@...el.com>,
	linux-kernel@...r.kernel.org, linux-acpi@...r.kernel.org,
	jmoyer@...hat.com, axboe@...nel.dk, linux-api@...r.kernel.org,
	akpm@...ux-foundation.org, hch@....de
Subject: Re: [PATCH v6 11/21] libnvdimm, nfit: add interleave-set state-tracking infrastructure

On Thursday, June 11, 2015 04:11:09 PM Dan Williams wrote:
> On platforms that have firmware support for reading/writing per-dimm
> label space, a portion of the dimm may be accessible via an interleave
> set PMEM mapping in addition to the dimm's BLK (block-data-window
> aperture(s)) interface.  A label, stored in a "configuration data
> region" on the dimm, disambiguates which dimm addresses are accessed
> through which exclusive interface.
> 
> Add infrastructure that allows the kernel to block modifications to a
> label in the set while any member dimm is active.  Note that this is
> meant only for enforcing "no modifications of active labels" via the
> coarse ioctl command.  Adding/deleting namespaces from an active
> interleave set is always possible via sysfs.
> 
> Another aspect of tracking interleave sets is tracking their integrity
> when DIMMs in a set are physically re-ordered.  For this purpose we
> generate an "interleave-set cookie" that can be recorded in a label and
> validated against the current configuration.  It is the bus provider
> implementation's responsibility to calculate the interleave set cookie
> and attach it to a given region.
> 
> Cc: Neil Brown <neilb@...e.de>
> Cc: <linux-acpi@...r.kernel.org>
> Cc: Greg KH <gregkh@...uxfoundation.org>
> Cc: Robert Moore <robert.moore@...el.com>
> Cc: Rafael J. Wysocki <rafael.j.wysocki@...el.com>
> Signed-off-by: Dan Williams <dan.j.williams@...el.com>

For the ACPI part:

Acked-by: Rafael J. Wysocki <rafael.j.wysocki@...el.com>

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/