Received: by 10.223.176.5 with SMTP id f5csp3791640wra; Mon, 29 Jan 2018 19:54:58 -0800 (PST) X-Google-Smtp-Source: AH8x224blS7QTD3lgX8pX1aNwwW4LGooNOanMPZyc54Qoa394veNSY8YKewJXgLsOLyPzKS6BqGV X-Received: by 10.99.38.67 with SMTP id m64mr15711403pgm.2.1517284498356; Mon, 29 Jan 2018 19:54:58 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1517284498; cv=none; d=google.com; s=arc-20160816; b=yqhD5QSakkEoso+O87AJr8p43nMNBmHewixYjkH9eKyjY4Zlp2aKKJtFc1NVfZeV4L I8DHGav6y86TZXeBIGOP37tOyy573IaUboMeHJ9GpvUEqyaTH1ABI/y7XpWs0x57gmNU /XqliIKbTDai1SPVv5E8TmmwRG7q7TMpdKoQ7ipUTPVRBm40kWNThOMi/nBraMybbhfa yDVQvnuuJ5J5Wt0A6sSAxSXPgek8T6xbZSG4WTY6etinjxAPMbnx27zA7m12DJvZRc9Y oX0ibxfY+Y/fOV09dcAWWinQPzSGEY9UqCZnniAN3EvFEKgdDY9Pc2/sh6cJV8XclHzi vG0w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:references:in-reply-to:message-id:date :subject:cc:to:from:dkim-signature:arc-authentication-results; bh=WmGeZYw6t7M8rMJkYr5juAGDANGi/LKLZXWzZoA6Ps4=; b=qjOAKjoI7y+khUkhRdb/q51IGJomUhC/ocw/wk2vYj6TXE1HR0L3PDYkwAa0hSxWyS nzbJAvFQjm5VzMSh53rIU9ILxBs1JK4ddk8XD9kqlFnwNbFTZt1AD9wfPD5wrz99CtBV 9QlYMuPuFSet0mDwM6L0ZEtF0nt2lJxnjPCi+0IHS8Vb5j6a3htNRusEobXPzBniLJaZ u9exJ2nsLopMy6jZkihiNqOgMMy+1Doi52Ob7jSpOQsJ5PXDPW3OD50pOTq71hXPrfqK LxM0yJMdDoGeij6X5beoUcO0m9BtLk9ioHc9NfRzhl7G7qH0uyiusb9z0grMmfJ5s9+t LiRw== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@gmail.com header.s=20161025 header.b=hcYaCKJ6; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id t66si967982pgc.653.2018.01.29.19.54.42; Mon, 29 Jan 2018 19:54:58 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=fail header.i=@gmail.com header.s=20161025 header.b=hcYaCKJ6; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752401AbeA3DyQ (ORCPT + 99 others); Mon, 29 Jan 2018 22:54:16 -0500 Received: from mail-pg0-f68.google.com ([74.125.83.68]:34316 "EHLO mail-pg0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752200AbeA3DyO (ORCPT ); Mon, 29 Jan 2018 22:54:14 -0500 Received: by mail-pg0-f68.google.com with SMTP id r19so6194722pgn.1 for ; Mon, 29 Jan 2018 19:54:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:from:to:cc:subject:date:message-id:in-reply-to:references; bh=WmGeZYw6t7M8rMJkYr5juAGDANGi/LKLZXWzZoA6Ps4=; b=hcYaCKJ6tNl5KBW1sQBd9aBuw2lkn4rpNh/B6kG12V6jhjpjCWX24+GBpulRjt6Zg5 msYd+rRGnlaHcn1pJqIZzpj4txbHqjXzo8hsrhnkf8yoytY4Xp9rcO4tyJ48hPCKGcnt Vxfr3Y8SphhaatvRozkIeWNAztqXk4Bbcl6lqCkf9QyYUBY7YsyrircjAV6MaFluG2GG FsMB2fElW2FSOag3JAwSP7AV6zA2UhuyRe/lgd4KT9xZhl7zMoIPJS2/C7ugjMzIRO0R 8awVxxfWAirf6TQ2/2wu0uf26UwPvrKR+5zPka4JAX64itBcxXVnxpJ2TMjgQHKrTmKA SLAg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:from:to:cc:subject:date:message-id :in-reply-to:references; bh=WmGeZYw6t7M8rMJkYr5juAGDANGi/LKLZXWzZoA6Ps4=; b=FnlqX7xj14UlSgDcpkDb7s8brvXiB1zP8yvZxG/dc9Q9v2liICwk4AtGtUUVF8PN5S gBfVKdFcD02oVjtzjW97QhDVcMGdjy5RfMa2KGT/w6j/pvzC0QFMsQros9U84yCvkxbQ YHecKV1H5K+nE7Z2uj7naRTgaqFfgm7xPRCvQpifaDugC6mi9hdI/ODW5+RgrCtQxUAL FYfg63kfECGVEsZw9zbYRi18YvnNQo4m06KifS1UNYt0Nsz7iJDw6Zg3jcbEifC6BXx+ 6ycqEIigxt9WNTsRwj2eWC6gAsXQpsTrV4kQjTE2i0WuL9MP8GYuRI7/aYigopYB9tGI ClBw== X-Gm-Message-State: AKwxyteyUUTibJFOaLM3K54bdC9jrkqBtmEIepOg+aMVkUsdQfQLsDF5 adDsU09IyWhAIEJ/5pMikA== X-Received: by 2002:a17:902:8e8a:: with SMTP id bg10-v6mr24523836plb.162.1517284454005; Mon, 29 Jan 2018 19:54:14 -0800 (PST) Received: from www9186uo.sakura.ne.jp (www9186uo.sakura.ne.jp. [153.121.56.200]) by smtp.gmail.com with ESMTPSA id 137sm18622043pge.74.2018.01.29.19.54.11 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 29 Jan 2018 19:54:13 -0800 (PST) From: Naoya Horiguchi To: linux-mm@kvack.org Cc: Andrew Morton , Michal Hocko , Mike Kravetz , "Aneesh Kumar K.V" , Anshuman Khandual , linux-kernel@vger.kernel.org Subject: [PATCH v2] mm: hwpoison: disable memory error handling on 1GB hugepage Date: Tue, 30 Jan 2018 12:54:04 +0900 Message-Id: <1517284444-18149-1-git-send-email-n-horiguchi@ah.jp.nec.com> X-Mailer: git-send-email 2.7.0 In-Reply-To: <20180130013919.GA19959@hori1.linux.bs1.fc.nec.co.jp> References: <20180130013919.GA19959@hori1.linux.bs1.fc.nec.co.jp> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Recently the following BUG was reported: Injecting memory failure for pfn 0x3c0000 at process virtual address 0x7fe300000000 Memory failure: 0x3c0000: recovery action for huge page: Recovered BUG: unable to handle kernel paging request at ffff8dfcc0003000 IP: gup_pgd_range+0x1f0/0xc20 PGD 17ae72067 P4D 17ae72067 PUD 0 Oops: 0000 [#1] SMP PTI ... CPU: 3 PID: 5467 Comm: hugetlb_1gb Not tainted 4.15.0-rc8-mm1-abc+ #3 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.9.3-1.fc25 04/01/2014 You can easily reproduce this by calling madvise(MADV_HWPOISON) twice on a 1GB hugepage. This happens because get_user_pages_fast() is not aware of a migration entry on pud that was created in the 1st madvise() event. I think that conversion to pud-aligned migration entry is working, but other MM code walking over page table isn't prepared for it. We need some time and effort to make all this work properly, so this patch avoids the reported bug by just disabling error handling for 1GB hugepage. Signed-off-by: Naoya Horiguchi Acked-by: Michal Hocko // for v1 Cc: --- ChangeLog v1 -> v2: - add comment about what we need to support hwpoision for pud-sized hugetlb - use "page size > PMD_SIZE" condition instead of hstate_is_gigantic() --- include/linux/mm.h | 1 + mm/memory-failure.c | 16 ++++++++++++++++ 2 files changed, 17 insertions(+) diff --git v4.15-rc8-mmotm-2018-01-18-16-31/include/linux/mm.h v4.15-rc8-mmotm-2018-01-18-16-31_patched/include/linux/mm.h index 63f7ba1..6b3df81 100644 --- v4.15-rc8-mmotm-2018-01-18-16-31/include/linux/mm.h +++ v4.15-rc8-mmotm-2018-01-18-16-31_patched/include/linux/mm.h @@ -2607,6 +2607,7 @@ enum mf_action_page_type { MF_MSG_POISONED_HUGE, MF_MSG_HUGE, MF_MSG_FREE_HUGE, + MF_MSG_NON_PMD_HUGE, MF_MSG_UNMAP_FAILED, MF_MSG_DIRTY_SWAPCACHE, MF_MSG_CLEAN_SWAPCACHE, diff --git v4.15-rc8-mmotm-2018-01-18-16-31/mm/memory-failure.c v4.15-rc8-mmotm-2018-01-18-16-31_patched/mm/memory-failure.c index d530ac1..264e020 100644 --- v4.15-rc8-mmotm-2018-01-18-16-31/mm/memory-failure.c +++ v4.15-rc8-mmotm-2018-01-18-16-31_patched/mm/memory-failure.c @@ -508,6 +508,7 @@ static const char * const action_page_types[] = { [MF_MSG_POISONED_HUGE] = "huge page already hardware poisoned", [MF_MSG_HUGE] = "huge page", [MF_MSG_FREE_HUGE] = "free huge page", + [MF_MSG_NON_PMD_HUGE] = "non-pmd-sized huge page", [MF_MSG_UNMAP_FAILED] = "unmapping failed page", [MF_MSG_DIRTY_SWAPCACHE] = "dirty swapcache page", [MF_MSG_CLEAN_SWAPCACHE] = "clean swapcache page", @@ -1090,6 +1091,21 @@ static int memory_failure_hugetlb(unsigned long pfn, int trapno, int flags) return 0; } + /* + * TODO: hwpoison for pud-sized hugetlb doesn't work right now, so + * simply disable it. In order to make it work properly, we need + * make sure that: + * - conversion of a pud that maps an error hugetlb into hwpoison + * entry properly works, and + * - other mm code walking over page table is aware of pud-aligned + * hwpoison entries. + */ + if (huge_page_size(page_hstate(head)) > PMD_SIZE) { + action_result(pfn, MF_MSG_NON_PMD_HUGE, MF_IGNORED); + res = -EBUSY; + goto out; + } + if (!hwpoison_user_mappings(p, pfn, trapno, flags, &head)) { action_result(pfn, MF_MSG_UNMAP_FAILED, MF_IGNORED); res = -EBUSY; -- 2.7.0