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
| ||
|
Date: Mon, 2 Dec 2013 10:32:52 +0800 From: Dave Young <dyoung@...hat.com> To: Borislav Petkov <bp@...en8.de> Cc: Matt Fleming <matt@...sole-pimps.org>, linux-kernel@...r.kernel.org, linux-efi@...r.kernel.org, x86@...nel.org, mjg59@...f.ucam.org, hpa@...or.com, James.Bottomley@...senPartnership.com, vgoyal@...hat.com, ebiederm@...ssion.com, horms@...ge.net.au, kexec@...ts.infradead.org, greg@...ah.com, toshi.kani@...com Subject: Re: [PATCH v4 00/12] kexec kernel efi runtime support On 11/29/13 at 06:02pm, Borislav Petkov wrote: > On Fri, Nov 29, 2013 at 04:28:22PM +0800, Dave Young wrote: > > I think for anyone who are using early_memremap should know this is a > > normal kernel memory instead of real __iomem > > You can never ever assume that people are using kernel interfaces > correctly. But the semantic of early_memreamp should be that it will just return a normal memory pointer instead of iomem so the fix to convert the internal implementation to return a __force __kernel make sense to me. For iounmap I think since we have early_memremap, we have reason to add early_memunmap() so sparse will be happy. Thanks Dave -- 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/
Powered by blists - more mailing lists