linux-kernel - [PATCH 0/3] /dev/mem as optional device + associated tidy up

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:	Sun,  7 Dec 2014 15:40:32 +0000
From:	robert.ward114@...glemail.com
To:	arnd@...db.de, gregkh@...uxfoundation.org,
	linux-kernel@...r.kernel.org
Cc:	Rob Ward <robert.ward114@...glemail.com>
Subject: [PATCH 0/3] /dev/mem as optional device + associated tidy up

From: Rob Ward <robert.ward114@...glemail.com>

Makes the /dev/mem device optional using the CONFIG_DEVMEM option.

This brings /dev/mem in line with /dev/kmem so it can de disabled. 
Disabling /dev/mem is preferable on devices that do not require
direct access to memory in order to improve security. This is especially
true on platforms where no restiction is placed on the areas of memory
that can be accessed(for example mips) without custom modifcations to
the kernel source.

The implementation of this functionality declares the mem_fops structure
as __maybe_unused to eliminate the need for #ifdefs throughout the
file.

Follow up changes are present to change CONFIG_DEVKMEM and CONFIG_DEVPORT
to use __maybe_unused. This simplifies the code and make the
implementations consistent.

Rob Ward (3):
  drivers: char: mem: Make /dev/mem an optional device
  drivers: char: mem: Simplify DEVKMEM configuration
  drivers: char: mem: Simplify DEVPORT configuration

 drivers/char/Kconfig |  9 +++++++++
 drivers/char/mem.c   | 18 +++++-------------
 2 files changed, 14 insertions(+), 13 deletions(-)

-- 
2.0.2

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