[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1358854984-6073-1-git-send-email-tangchen@cn.fujitsu.com>
Date: Tue, 22 Jan 2013 19:42:59 +0800
From: Tang Chen <tangchen@...fujitsu.com>
To: akpm@...ux-foundation.org, rientjes@...gle.com,
len.brown@...el.com, benh@...nel.crashing.org, paulus@...ba.org,
cl@...ux.com, minchan.kim@...il.com,
kosaki.motohiro@...fujitsu.com, isimatu.yasuaki@...fujitsu.com,
wujianguo@...wei.com, wency@...fujitsu.com, hpa@...or.com,
linfeng@...fujitsu.com, laijs@...fujitsu.com, mgorman@...e.de,
yinghai@...nel.org, glommer@...allels.com, jiang.liu@...wei.com,
julian.calaby@...il.com, sfr@...b.auug.org.au
Cc: x86@...nel.org, linux-mm@...ck.org, linux-kernel@...r.kernel.org,
linuxppc-dev@...ts.ozlabs.org, linux-acpi@...r.kernel.org
Subject: [PATCH Bug fix 0/5] Bug fix for physical memory hot-remove.
Here are some bug fix patches for physical memory hot-remove. All these
patches are based on the latest -mm tree.
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git akpm
And patch1 and patch3 are very important.
patch1: free compound pages when freeing memmap, otherwise the kernel
will panic the next time memory is hot-added.
patch3: the old way of freeing pagetable pages was wrong. We should never
split larger pages into small ones.
Lai Jiangshan (1):
Bug-fix: mempolicy: fix is_valid_nodemask()
Tang Chen (3):
Bug fix: Do not split pages when freeing pagetable pages.
Bug fix: Fix section mismatch problem of
release_firmware_map_entry().
Bug fix: Fix the doc format in drivers/firmware/memmap.c
Wen Congyang (1):
Bug fix: consider compound pages when free memmap
arch/x86/mm/init_64.c | 148 ++++++++++++++-------------------------------
drivers/firmware/memmap.c | 16 +++---
mm/mempolicy.c | 36 +++++++----
mm/sparse.c | 2 +-
4 files changed, 77 insertions(+), 125 deletions(-)
--
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