linux-kernel - Re: [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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <8719187.RB9WVc9E5S@wuerfel>
Date:	Sun, 07 Dec 2014 20:35:31 +0100
From:	Arnd Bergmann <arnd@...db.de>
To:	robert.ward114@...glemail.com
Cc:	gregkh@...uxfoundation.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/3] /dev/mem as optional device + associated tidy up

On Sunday 07 December 2014 15:40:32 robert.ward114@...glemail.com wrote:
> 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.
> 

Acked-by: Arnd Bergmann <arnd@...db.de>
--
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/