linux-kernel - Introduction to rar_register patch set of 5 patches

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]

Message-Id: <1264182811-28933-1-git-send-email-mark.a.allyn@intel.com>
Date:	Fri, 22 Jan 2010 09:53:30 -0800
From:	Mark Allyn <mark.a.allyn@...el.com>
To:	linux-kernel@...r.kernel.org, greg@...ah.com, alan@...ux.intel.com,
	charles.f.johnson@...el.com
Cc:	Mark Allyn <mark.a.allyn@...el.com>
Subject: Introduction to rar_register patch set of 5 patches

The following five 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 five patches. They are:

Patch 1 of 5 for rar_register; renaming to rar_register
	This renames the current rar resigter driver to
	the name rar_register. This is to differentiate
	it from the rar_handler driver, which will be
	submitted later.
Patch 2 of 5 for rar_register - renaming directory to rar_register
	This renames the directory in which the driver files
	are located; again for clarity.
Patch 3 of 5 for rar_register - provide better explanation in Kconfig
	This patch provides a better explanation of what this
	driver is for in the Kconfig file
Patch 4 of 5 for rar_register - fix checkpatch errors and debug header
	This patch cleans up checkpatch errors and warnings as well as
	fixes bugs in the rar_register.h header file
Patch 5 of 5 for rar_register - fix checkpatch errors and debug program file
	This patch cleans up checkpatch errors and warnings as well as
	fixes bugs in the rar_register.c program file

Please note that patches 1, 2, and 3 are for 'housekeeping'. They do nothing
to correct any checkpatch errors/warnings in the driver.

Patches 4 and 5 clean up checkpatch issues in the rar_register.h and
rar_register.c file respectively.

After patch 5 is applied, there should be no checkpatch issues in the entire
driver directory

Please note that I did a test build of this patch set after patch 3 and after
patch 5 of this set.

If there are issues with either patch 4 or patch 5, you can still submit 
patches 1, 2, and 3 and expect a clean build.

These patches were applied against the kernel next that I pulled as of Wednesday, 
January 21, 2010.

Mark Allyn
mark.a.allyn@...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/