From: Miaohe Lin <linmiaohe@huawei.com>
To: Jiaqi Yan <jiaqiyan@google.com>, <akpm@linux-foundation.org>,
<mike.kravetz@oracle.com>, <naoya.horiguchi@nec.com>
Cc: <songmuchun@bytedance.com>, <shy828301@gmail.com>,
<linux-mm@kvack.org>, <linux-kernel@vger.kernel.org>,
<duenwen@google.com>, <axelrasmussen@google.com>,
<jthoughton@google.com>
Subject: Re: [PATCH v3 2/4] mm/hwpoison: check if a subpage of a hugetlb folio is raw HWPOISON
Date: Sat, 8 Jul 2023 10:57:00 +0800 [thread overview]
Message-ID: <6682284d-7ad3-9b59-687d-899f4d08d911@huawei.com> (raw)
In-Reply-To: <20230707201904.953262-3-jiaqiyan@google.com>
On 2023/7/8 4:19, Jiaqi Yan wrote:
> Add the functionality, is_raw_hwp_subpage, to tell if a subpage of a
> hugetlb folio is a raw HWPOISON page. This functionality relies on
> RawHwpUnreliable to be not set; otherwise hugepage's raw HWPOISON list
> becomes meaningless.
>
> is_raw_hwp_subpage needs to hold hugetlb_lock in order to synchronize
> with __get_huge_page_for_hwpoison, who iterates and inserts an entry to
> raw_hwp_list. llist itself doesn't ensure insertion is synchornized with
> the iterating used by __is_raw_hwp_list. Caller can minimize the
> overhead of lock cycles by first checking if folio / head page's
> HWPOISON flag is set.
>
> Exports this functionality to be immediately used in the read operation
> for hugetlbfs.
>
> Reviewed-by: Mike Kravetz <mike.kravetz@oracle.com>
> Reviewed-by: Naoya Horiguchi <naoya.horiguchi@nec.com>
> Signed-off-by: Jiaqi Yan <jiaqiyan@google.com>
> ---
> include/linux/hugetlb.h | 19 +++++++++++++++++++
> include/linux/mm.h | 7 +++++++
> mm/hugetlb.c | 10 ++++++++++
> mm/memory-failure.c | 34 ++++++++++++++++++++++++----------
> 4 files changed, 60 insertions(+), 10 deletions(-)
> ...
> -static inline struct llist_head *raw_hwp_list_head(struct folio *folio)
> +bool __is_raw_hwp_subpage(struct folio *folio, struct page *subpage)
> {
> - return (struct llist_head *)&folio->_hugetlb_hwpoison;
> + struct llist_head *raw_hwp_head;
> + struct raw_hwp_page *p, *tmp;
> + bool ret = false;
> +
> + if (!folio_test_hwpoison(folio))
> + return false;
> +
> + /*
> + * When RawHwpUnreliable is set, kernel lost track of which subpages
> + * are HWPOISON. So return as if ALL subpages are HWPOISONed.
> + */
> + if (folio_test_hugetlb_raw_hwp_unreliable(folio))
> + return true;
> +
> + raw_hwp_head = raw_hwp_list_head(folio);
> + llist_for_each_entry_safe(p, tmp, raw_hwp_head->first, node) {
Since we don't free the raw_hwp_list, does llist_for_each_entry works same as llist_for_each_entry_safe?
> + if (subpage == p->page) {
> + ret = true;
> + break;
> + }
> + }
> +
> + return ret;
> }
It seems there's a race between __is_raw_hwp_subpage and unpoison_memory:
unpoison_memory __is_raw_hwp_subpage
if (!folio_test_hwpoison(folio)) -- hwpoison is set
folio_free_raw_hwp llist_for_each_entry_safe raw_hwp_list
llist_del_all ..
folio_test_clear_hwpoison
But __is_raw_hwp_subpage is used in hugetlbfs, unpoison_memory couldn't reach here because there's a
folio_mapping == NULL check before folio_free_raw_hwp.
Anyway, this patch looks good to me.
Reviewed-by: Miaohe Lin <linmiaohe@huawei.com>
Thanks.
next prev parent reply other threads:[~2023-07-08 2:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-07 20:19 [PATCH v3 0/4] Improve hugetlbfs read on HWPOISON hugepages Jiaqi Yan
2023-07-07 20:19 ` [PATCH v3 1/4] mm/hwpoison: delete all entries before traversal in __folio_free_raw_hwp Jiaqi Yan
2023-07-08 2:40 ` Miaohe Lin
2023-07-07 20:19 ` [PATCH v3 2/4] mm/hwpoison: check if a subpage of a hugetlb folio is raw HWPOISON Jiaqi Yan
2023-07-07 20:31 ` Matthew Wilcox
2023-07-07 21:05 ` Andrew Morton
2023-07-10 0:21 ` Naoya Horiguchi
2023-07-10 15:11 ` Jiaqi Yan
2023-07-11 8:59 ` Naoya Horiguchi
2023-07-08 2:57 ` Miaohe Lin [this message]
2023-07-10 15:16 ` Jiaqi Yan
2023-07-11 17:05 ` Jiaqi Yan
2023-07-11 18:01 ` Mike Kravetz
2023-07-11 22:22 ` Jiaqi Yan
2023-07-12 2:25 ` Miaohe Lin
2023-07-07 20:19 ` [PATCH v3 3/4] hugetlbfs: improve read HWPOISON hugepage Jiaqi Yan
2023-07-07 20:19 ` [PATCH v3 4/4] selftests/mm: add tests for HWPOISON hugetlbfs read Jiaqi Yan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6682284d-7ad3-9b59-687d-899f4d08d911@huawei.com \
--to=linmiaohe@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=axelrasmussen@google.com \
--cc=duenwen@google.com \
--cc=jiaqiyan@google.com \
--cc=jthoughton@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@oracle.com \
--cc=naoya.horiguchi@nec.com \
--cc=shy828301@gmail.com \
--cc=songmuchun@bytedance.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox