| 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
| ||
|
Message-Id: <20090603184639.1933B1D028F@basil.firstfloor.org> Date: Wed, 3 Jun 2009 20:46:38 +0200 (CEST) From: Andi Kleen <andi@...stfloor.org> To: akpm@...ux-foundation.org, npiggin@...e.de, linux-kernel@...r.kernel.org, linux-mm@...ck.org, fengguang.wu@...el.com Subject: [PATCH] [6/16] HWPOISON: Add various poison checks in mm/memory.c Bail out early when hardware poisoned pages are found in page fault handling. Since they are poisoned they should not be mapped freshly into processes, because that would cause another (potentially deadly) machine check This is generally handled in the same way as OOM, just a different error code is returned to the architecture code. Signed-off-by: Andi Kleen <ak@...ux.intel.com> --- mm/memory.c | 3 +++ 1 file changed, 3 insertions(+) Index: linux/mm/memory.c =================================================================== --- linux.orig/mm/memory.c 2009-06-03 19:36:23.000000000 +0200 +++ linux/mm/memory.c 2009-06-03 19:36:23.000000000 +0200 @@ -2797,6 +2797,9 @@ if (unlikely(ret & (VM_FAULT_ERROR | VM_FAULT_NOPAGE))) return ret; + if (unlikely(PageHWPoison(vmf.page))) + return VM_FAULT_HWPOISON; + /* * For consistency in subsequent calls, make the faulted page always * locked. -- 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