linux-kernel - Re: [PATCH v3 03/13] arm64: improve CONFIG_STRICT

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: <20141125173925.GE3331@console-pimps.org>
Date:	Tue, 25 Nov 2014 17:39:25 +0000
From:	Matt Fleming <matt@...sole-pimps.org>
To:	Ard Biesheuvel <ard.biesheuvel@...aro.org>
Cc:	leif.lindholm@...aro.org, roy.franz@...aro.org,
	linux-arm-kernel@...ts.infradead.org, mark.rutland@....com,
	msalter@...hat.com, dyoung@...hat.com, linux-efi@...r.kernel.org,
	matt.fleming@...el.com, will.deacon@....com,
	catalin.marinas@....com, grant.likely@...aro.org,
	geoff.levand@...aro.org, linux-kernel@...r.kernel.org,
	Borislav Petkov <bp@...en8.de>, Peter Jones <pjones@...hat.com>
Subject: Re: [PATCH v3 03/13] arm64: improve CONFIG_STRICT_DEVMEM handling

On Tue, 18 Nov, at 01:57:02PM, Ard Biesheuvel wrote:
> Improve the handling of /dev/mem mappings under CONFIG_STRICT_DEVMEM by:
> - allowing read-only access to parts of System RAM that are not
>   considered memory by the kernel, this is mainly intended for exposing
>   UEFI Configuration tables to userland;
> - avoid using non-cached mappings for those parts of System RAM, as it
>   may result in mismatched attributes.

Is this really the best way to expose EFI config tables?

We already have parts in /sys/firmware/efi/ and in particular we expose
the runtime mappings there for kexec on x86.

Hooking this into the /dev/mem infrastructure just seems wrong to me.

-- 
Matt Fleming, Intel Open Source Technology Center
--
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/