From: Jiaqi Yan <jiaqiyan@google.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: kirill.shutemov@linux.intel.com, kirill@shutemov.name,
tongtiangen@huawei.com, tony.luck@intel.com,
naoya.horiguchi@nec.com, linmiaohe@huawei.com,
linux-mm@kvack.org, Oscar Salvador <osalvador@suse.de>,
Yang Shi <shy828301@gmail.com>
Subject: Re: [PATCH v6 0/2] Memory poison recovery in khugepaged collapsing
Date: Thu, 17 Nov 2022 17:34:34 -0800 [thread overview]
Message-ID: <CACw3F52Xm5To-OZ6dTK6nHjZenrsYnB8Zm9hVZK6Hpd=wc=ZnQ@mail.gmail.com> (raw)
In-Reply-To: <20221116135243.b1db6b864efb89595d174be2@linux-foundation.org>
On Wed, Nov 16, 2022 at 1:52 PM Andrew Morton <akpm@linux-foundation.org> wrote:
>
> On Wed, 16 Nov 2022 09:58:23 -0800 Jiaqi Yan <jiaqiyan@google.com> wrote:
>
> > Thanks for ccing Oscar, Andrew.
> >
> > After getting this patch into our internal production environment, I
> > recently found a regression bug introduced by my commit a0157a2c735b
> > ("mm/khugepaged: recover from poisoned file-backed memory").
> > Given it is only in mm-unstable, I wonder should I put out a v7 with
> > the fix, or should I make it a new and separate commit?
>
> Either approach is OK. I usually convert replacement patches into
> deltas so I and others can see what changed. But people like to see
> the whole patch for review purposes, so I guess that if you email out a
> new version of the patch, we get to see both.
>
>
Thanks Andrew. I just sent out v7 with the fix.
prev parent reply other threads:[~2022-11-18 1:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-07 2:53 Jiaqi Yan
2022-11-07 2:53 ` [PATCH v6 1/2] mm/khugepaged: recover from poisoned anonymous memory Jiaqi Yan
2022-11-07 2:53 ` [PATCH v6 2/2] mm/khugepaged: recover from poisoned file-backed memory Jiaqi Yan
2022-11-07 20:53 ` [PATCH v6 0/2] Memory poison recovery in khugepaged collapsing Andrew Morton
2022-11-16 17:58 ` Jiaqi Yan
2022-11-16 21:52 ` Andrew Morton
2022-11-18 1:34 ` Jiaqi Yan [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='CACw3F52Xm5To-OZ6dTK6nHjZenrsYnB8Zm9hVZK6Hpd=wc=ZnQ@mail.gmail.com' \
--to=jiaqiyan@google.com \
--cc=akpm@linux-foundation.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=kirill@shutemov.name \
--cc=linmiaohe@huawei.com \
--cc=linux-mm@kvack.org \
--cc=naoya.horiguchi@nec.com \
--cc=osalvador@suse.de \
--cc=shy828301@gmail.com \
--cc=tongtiangen@huawei.com \
--cc=tony.luck@intel.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