From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759773AbZBLMlm (ORCPT ); Thu, 12 Feb 2009 07:41:42 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1758828AbZBLMil (ORCPT ); Thu, 12 Feb 2009 07:38:41 -0500 Received: from one.firstfloor.org ([213.235.205.2]:49215 "EHLO one.firstfloor.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758784AbZBLMih (ORCPT ); Thu, 12 Feb 2009 07:38:37 -0500 From: Andi Kleen References: <20090212137.750180365@firstfloor.org> In-Reply-To: <20090212137.750180365@firstfloor.org> To: ying.huang@intel.com, akpm@linux-foundation.org, x86@firstfloor.org, linux-kernel@vger.kernel.org Subject: [PATCH] [9/10] x86: MCE: Fix a race condition in mce_read(). Message-Id: <20090212123728.676E03E666F@basil.firstfloor.org> Date: Thu, 12 Feb 2009 13:37:28 +0100 (CET) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Huang Ying Impact: bugfix Considering the situation as follow: before: mcelog.next == 1, mcelog.entry[0].finished = 1 +-------------------------------------------------------------------------- R W1 W2 W3 read mcelog.next (1) mcelog.next++ (2) (working on entry 1, finished == 0) mcelog.next = 0 mcelog.next++ (1) (working on entry 0) mcelog.next++ (2) (working on entry 1) <----------------- race ----------------> (done on entry 1, finished = 1) (done on entry 1, finished = 1) To fix the race condition, a cmpxchg loop is added to mce_read() to ensure no new MCE record can be added between mcelog.next reading and mcelog.next = 0. Signed-off-by: Huang Ying Signed-off-by: Andi Kleen