summaryrefslogtreecommitdiffstats
path: root/Documentation/i2o
diff options
context:
space:
mode:
authorNaoya Horiguchi <n-horiguchi@ah.jp.nec.com>2014-02-10 14:25:50 -0800
committerLinus Torvalds <torvalds@linux-foundation.org>2014-02-10 16:01:43 -0800
commit8d547ff4ac5927245e0833ac18528f939da0ee0e (patch)
treedf35c19621783cd0c0c8735aab27eed555e48441 /Documentation/i2o
parentfb37bb04d6c8d6c44e61d9da189dcfa6aa0f135e (diff)
downloadop-kernel-dev-8d547ff4ac5927245e0833ac18528f939da0ee0e.zip
op-kernel-dev-8d547ff4ac5927245e0833ac18528f939da0ee0e.tar.gz
mm/memory-failure.c: move refcount only in !MF_COUNT_INCREASED
mce-test detected a test failure when injecting error to a thp tail page. This is because we take page refcount of the tail page in madvise_hwpoison() while the fix in commit a3e0f9e47d5e ("mm/memory-failure.c: transfer page count from head page to tail page after split thp") assumes that we always take refcount on the head page. When a real memory error happens we take refcount on the head page where memory_failure() is called without MF_COUNT_INCREASED set, so it seems to me that testing memory error on thp tail page using madvise makes little sense. This patch cancels moving refcount in !MF_COUNT_INCREASED for valid testing. [akpm@linux-foundation.org: s/&&/&/] Signed-off-by: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com> Cc: Andi Kleen <andi@firstfloor.org> Cc: Wanpeng Li <liwanp@linux.vnet.ibm.com> Cc: Chen Gong <gong.chen@linux.intel.com> Cc: <stable@vger.kernel.org> [3.9+: a3e0f9e47d5e] Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'Documentation/i2o')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud