From: Naoya Horiguchi <naoya.horiguchi@linux.dev>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, Mike Kravetz <mike.kravetz@oracle.com>,
Miaohe Lin <linmiaohe@huawei.com>, Yang Shi <shy828301@gmail.com>,
Dan Carpenter <dan.carpenter@oracle.com>,
Naoya Horiguchi <naoya.horiguchi@nec.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v8 0/3] mm/hwpoison: fix race between hugetlb free/demotion and memory_failure_hugetlb()
Date: Sat, 9 Apr 2022 11:31:24 +0900 [thread overview]
Message-ID: <20220409023124.GA1649696@u2004> (raw)
In-Reply-To: <20220408164755.3ef6536c1cdcb38955348a2c@linux-foundation.org>
On Fri, Apr 08, 2022 at 04:47:55PM -0700, Andrew Morton wrote:
> On Fri, 8 Apr 2022 22:53:20 +0900 Naoya Horiguchi <naoya.horiguchi@linux.dev> wrote:
>
> > I updated v7 (https://lore.kernel.org/linux-mm/20220407112929.1344748-1-naoya.horiguchi@linux.dev/)
> > based on the comment from Miaohe Lin. Now I have a few additional patches.
> > Any comments and suggestions are welcomed.
>
> As [1/3] is cc:stable I queued that for 5.18-rcX and the other two
> patches I queued for 5.19.
>
> This plan means that [1/3] will be merged into mainline without the
> other two patches yet present, which is a combination which you may not
> have tested. Please confirm that this will be OK?
Yes, the plan is fine to me.
I've tested the kernel with all 3 patched, but 2/3 and 3/3 are simple and
the effect should be predictable. I'll test only with 1/3 next week.
Thanks,
Naoya Horiguchi
prev parent reply other threads:[~2022-04-09 2:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-08 13:53 [PATCH v8 0/3] mm/hwpoison: fix race between hugetlb free/demotion and memory_failure_hugetlb() Naoya Horiguchi
2022-04-08 13:53 ` [PATCH v8 1/3] " Naoya Horiguchi
2022-04-09 2:33 ` Miaohe Lin
2022-04-14 17:56 ` Mike Kravetz
2022-04-15 1:55 ` Miaohe Lin
2022-04-15 2:12 ` HORIGUCHI NAOYA(堀口 直也)
2022-04-15 4:18 ` [PATCH 4/3] mm, hugetlb, hwpoison: separate branch for free and in-use hugepage Naoya Horiguchi
2022-04-15 15:11 ` Mike Kravetz
2022-04-16 1:06 ` Miaohe Lin
2022-04-08 13:53 ` [PATCH v8 2/3] mm/hwpoison: put page in already hwpoisoned case with MF_COUNT_INCREASED Naoya Horiguchi
2022-04-09 2:04 ` Miaohe Lin
2022-04-14 19:41 ` Mike Kravetz
2022-04-08 13:53 ` [PATCH v8 3/3] Revert "mm/memory-failure.c: fix race with changing page compound again" Naoya Horiguchi
2022-04-09 2:07 ` Miaohe Lin
2022-04-14 17:59 ` Mike Kravetz
2022-04-08 23:47 ` [PATCH v8 0/3] mm/hwpoison: fix race between hugetlb free/demotion and memory_failure_hugetlb() Andrew Morton
2022-04-09 2:31 ` Naoya Horiguchi [this message]
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=20220409023124.GA1649696@u2004 \
--to=naoya.horiguchi@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=dan.carpenter@oracle.com \
--cc=linmiaohe@huawei.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 \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.