linux-kernel - Patch set for Restricted Access Region Register driver

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>] [day] [month] [year] [list]

Message-Id: <1265395912-15918-1-git-send-email-mark.a.allyn@intel.com>
Date:	Fri,  5 Feb 2010 10:51:52 -0800
From:	Mark Allyn <mark.a.allyn@...el.com>
To:	linux-kernel@...r.kernel.org, alan@...ux.intel.com,
	charles.f.johnson@...el.com, greg@...ah.com
Cc:	Mark Allyn <mark.a.allyn@...el.com>
Subject: Patch set for Restricted Access Region Register driver

The following six patches are for the Restricted Access Region
Register (rar_register) driver.

This driver is for the Intel MID platform.

Restricted access regions are regions of memory that can be
locked so that the x86 processor cannot access them. However,
peripheral devices with DMA can access them.

Restricted access regions are used to protect sensitive 
information from access by unauthorized software running
on the x86 processor.

The scenario is that encrypted information is presented to
an encryption/decryption device. That device in turn does
decryption of the information and places into one of the
restricted access regions. Another device can then access
and use the decrypted information. The x86 processor, however,
cannot see that data.

The rar_register driver provides address information for the
individual restricted access regions to other device driver
that need to use the regions. 

The rar_register also locks restricted access regions upon
request by other device drivers. 

The rar_register device does not interact with user space
processes at all. It only ineracts with other device driver.

There are six patches:

1 renaming driver to rar_register
2 renaming directory to rar_register
3 provide better explanation in Kconfig
4 fix checkpatch errors and debug header file
5 fix checkpatch errors and debug program file
6 add suspend and resume functions

Patches 1 and 2 are for renaming the driver from
rar to rar_register. They do not fix checkpatch issues.

A sucessful build was completed following all of these
patches.

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