From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933076AbZE0UOz (ORCPT ); Wed, 27 May 2009 16:14:55 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1760757AbZE0UMj (ORCPT ); Wed, 27 May 2009 16:12:39 -0400 Received: from one.firstfloor.org ([213.235.205.2]:35918 "EHLO one.firstfloor.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1761280AbZE0UMj (ORCPT ); Wed, 27 May 2009 16:12:39 -0400 From: Andi Kleen References: <200905271012.668777061@firstfloor.org> In-Reply-To: <200905271012.668777061@firstfloor.org> To: akpm@linux-foundation.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, fengguang.wu@intel.com Subject: [PATCH] [7/16] HWPOISON: Add various poison checks in mm/memory.c Message-Id: <20090527201233.5A2F61D0286@basil.firstfloor.org> Date: Wed, 27 May 2009 22:12:33 +0200 (CEST) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 --- mm/memory.c | 3 +++ 1 file changed, 3 insertions(+) Index: linux/mm/memory.c =================================================================== --- linux.orig/mm/memory.c 2009-05-27 21:14:21.000000000 +0200 +++ linux/mm/memory.c 2009-05-27 21:14:21.000000000 +0200 @@ -2659,6 +2659,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.