linux-kernel - [PATCH 0/6] SEP resynchronize

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:	Fri, 10 Feb 2012 13:52:13 +0000
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	greg@...ah.com, linux-kernel@...r.kernel.org,
	mark.a.allyn@...el.com
Subject: [PATCH 0/6] SEP resynchronize

This picks out and regenerates the changes between Intel internal tree work
and the upstream kernel. The big things here are the additional access modes
and the reworking of the kernel crypto interface to the device.

With these added the tree divergence is basically some 64bit warning fixes
only in the upstream tree, a few debug statements and some Android specific
bits.

---

Mark A. Allyn (6):
      sep: reworked crypto layer
      sep: NULL out pointers, mark debug code DEBUG to fix warnings
      sep: update initialisation
      sep: Add interfaces for the new functions
      sep: Basic infrastructure for SEP DMA access to non CPU regions
      sep: Add new PCI identifier


 drivers/staging/sep/sep_crypto.c         | 3058 ++++++++++++++++--------------
 drivers/staging/sep/sep_crypto.h         |   77 -
 drivers/staging/sep/sep_dev.h            |    3 
 drivers/staging/sep/sep_driver_api.h     |   15 
 drivers/staging/sep/sep_driver_hw_defs.h |    3 
 drivers/staging/sep/sep_main.c           |  337 +++
 6 files changed, 2015 insertions(+), 1478 deletions(-)

--
     "Knowledge has no value or use for the solitary owner: to be
      enjoyed it must be communicated" -- Charles Pratt, 1st Earl Camden

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