linux-kernel - [PATCH 0/3] Correctness fixes for NFIT BLK I/O path

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:	Wed,  8 Jul 2015 10:00:18 -0600
From:	Ross Zwisler <ross.zwisler@...ux.intel.com>
To:	linux-kernel@...r.kernel.org
Cc:	Ross Zwisler <ross.zwisler@...ux.intel.com>,
	Christoph Hellwig <hch@....de>,
	Dan Williams <dan.j.williams@...el.com>,
	Greg KH <gregkh@...uxfoundation.org>,
	Jeff Moyer <jmoyer@...hat.com>, Len Brown <lenb@...nel.org>,
	linux-acpi@...r.kernel.org, linux-nvdimm@...ts.01.org,
	"Rafael J. Wysocki" <rjw@...ysocki.net>,
	Toshi Kani <toshi.kani@...com>
Subject: [PATCH 0/3] Correctness fixes for NFIT BLK I/O path

Patch 1 is just a quick update to MAINTAINERS for include/linux/pmem.h.

Patches 2 and 3 in this series contain correctness fixes for the NFIT BLK I/O
path, which in my opinion need to be pulled in for v4.2.  These fixes include
making sure that the block control registers are properly flushed before the
associated apertures are accessed, which is necessary for proper operation.
This series also updates the I/O path to use non-temporal stores, and to
respect the "latch" flag outlined in the DSM specification.

Ross Zwisler (3):
  pmem: add maintainer for include/linux/pmem.h
  nfit: update block I/O path to use PMEM API
  nfit: add support for NVDIMM "latch" flag

 MAINTAINERS         |   1 +
 drivers/acpi/nfit.c | 114 +++++++++++++++++++++++++++++++++++++++++++++++++---
 drivers/acpi/nfit.h |  16 +++++++-
 3 files changed, 125 insertions(+), 6 deletions(-)

-- 
1.9.3

--
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/