From: Greg KH <gregkh@linuxfoundation.org>
To: Jane Chu <jane.chu@oracle.com>
Cc: stable@vger.kernel.org, tony.luck@intel.com,
dan.j.williams@intel.com, naoya.horiguchi@nec.com,
linmiaohe@huawei.com, glider@google.com
Subject: Re: [5.15/6.1-stable PATCH] Copy-on-write hwpoison recovery
Date: Wed, 28 Jun 2023 20:30:15 +0200 [thread overview]
Message-ID: <2023062803-expulsion-shrubs-4b49@gregkh> (raw)
In-Reply-To: <20230626230221.3064291-1-jane.chu@oracle.com>
On Mon, Jun 26, 2023 at 05:02:17PM -0600, Jane Chu wrote:
> I was able to reproduce crash on 5.15.y kernel during COW, and
> when the grandchild process attempts a write to a private page
> inherited from the child process and the private page contains
> a memory uncorrectable error. The way to reproduce is described
> in Tony's patch, using his ras-tools/einj_mem_uc.
> And the patch series fixed the panic issue in 5.15.y.
>
> Followed here is the backport of Tony patch series to stable 5.15
> and stable 6.1. Both backport have encountered trivial conflicts
> due to missing dependencies, details are provided in each patch.
>
> Please let me know whether the backport is acceptable.
Looks good to me, all now queued up, thanks!
greg k-h
prev parent reply other threads:[~2023-06-28 18:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-26 23:02 [5.15/6.1-stable PATCH] Copy-on-write hwpoison recovery Jane Chu
2023-06-26 23:02 ` [5.15-stable PATCH 1/2] mm, hwpoison: try to recover from copy-on write faults Jane Chu
2023-06-26 23:02 ` [5.15-stable PATCH 2/2] mm, hwpoison: when copy-on-write hits poison, take page offline Jane Chu
2023-06-26 23:02 ` [6.1-stable PATCH 1/2] mm, hwpoison: try to recover from copy-on write faults Jane Chu
2023-06-26 23:02 ` [6.1-stable PATCH 2/2] mm, hwpoison: when copy-on-write hits poison, take page offline Jane Chu
2023-06-28 18:30 ` Greg KH [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=2023062803-expulsion-shrubs-4b49@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=dan.j.williams@intel.com \
--cc=glider@google.com \
--cc=jane.chu@oracle.com \
--cc=linmiaohe@huawei.com \
--cc=naoya.horiguchi@nec.com \
--cc=stable@vger.kernel.org \
--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