Re: [PATCH 1/2] arch: consolidate CONFIG_STRICT_DEVM in lib/Kconfig.debug

From: Kees Cook
Date: Mon Nov 23 2015 - 13:56:33 EST

On Mon, Nov 23, 2015 at 9:12 AM, Dan Williams <dan.j.williams@xxxxxxxxx> wrote:
> On Mon, Nov 23, 2015 at 12:12 AM, Ingo Molnar <mingo@xxxxxxxxxx> wrote:
>> * Dan Williams <dan.j.williams@xxxxxxxxx> wrote:
>>> Let all the archs that implement CONFIG_STRICT_DEVM use a common
>>> definition in lib/Kconfig.debug.
>> For the x86 bit:
>> Acked-by: Ingo Molnar <mingo@xxxxxxxxxx>
>>> Note, the 'depends on !SPARC' is due to sparc not implementing
>>> devmem_is_allowed().
>> Maybe that should be converted into a helper Kconfig switch for architectures to
>> opt in to /dev/mem restrictions?
> Sure, easy enough to add a ARCH_HAS_DEVMEM_IS_ALLOWED opt-in.

Is there some hidden meaning about the difference between ARCH_HAS_...
and HAVE_ARCH_... and HAVE_... ?


Kees Cook
Chrome OS Security
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at