From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752842Ab0AVFTu (ORCPT ); Fri, 22 Jan 2010 00:19:50 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752330Ab0AVFTq (ORCPT ); Fri, 22 Jan 2010 00:19:46 -0500 Received: from mga02.intel.com ([134.134.136.20]:27965 "EHLO mga02.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751051Ab0AVFTb (ORCPT ); Fri, 22 Jan 2010 00:19:31 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.49,322,1262592000"; d="scan'208";a="486056847" Message-Id: <20100122051517.415742055@intel.com> User-Agent: quilt/0.48-1 Date: Fri, 22 Jan 2010 12:59:16 +0800 From: Wu Fengguang To: Andrew Morton cc: Greg Kroah-Hartman , Andi Kleen , Benjamin Herrenschmidt , Christoph Lameter , Ingo Molnar , Tejun Heo , Nick Piggin , KAMEZAWA Hiroyuki , , Wu Fengguang Cc: LKML cc: Linux Memory Management List , Subject: [PATCH 2/4] devmem: fix kmem write bug on memory holes References: <20100122045914.993668874@intel.com> Content-Disposition: inline; filename=vwrite-fix.patch Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org write_kmem() used to assume vwrite() always return the full buffer length. However now vwrite() could return 0 to indicate memory hole. This creates a bug that "buf" is not advanced accordingly. Fix it to simply ignore the return value, hence the memory hole. CC: Andi Kleen CC: Benjamin Herrenschmidt CC: Christoph Lameter CC: Ingo Molnar CC: Tejun Heo CC: Nick Piggin CC: KAMEZAWA Hiroyuki CC: Signed-off-by: Wu Fengguang --- drivers/char/mem.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) --- linux-mm.orig/drivers/char/mem.c 2010-01-11 10:32:32.000000000 +0800 +++ linux-mm/drivers/char/mem.c 2010-01-11 10:32:34.000000000 +0800 @@ -555,7 +555,7 @@ static ssize_t write_kmem(struct file * err = -EFAULT; break; } - sz = vwrite(kbuf, (char *)p, sz); + vwrite(kbuf, (char *)p, sz); count -= sz; buf += sz; virtr += sz;