From: Jane Chu <jane.chu@oracle.com>
To: stable@vger.kernel.org
Cc: tony.luck@intel.com, dan.j.williams@intel.com,
naoya.horiguchi@nec.com, linmiaohe@huawei.com, glider@google.com,
jane.chu@oracle.com
Subject: [5.15/6.1-stable PATCH] Copy-on-write hwpoison recovery
Date: Mon, 26 Jun 2023 17:02:17 -0600 [thread overview]
Message-ID: <20230626230221.3064291-1-jane.chu@oracle.com> (raw)
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.
Tony Luck (2):
mm, hwpoison: try to recover from copy-on write faults
mm, hwpoison: when copy-on-write hits poison, take page offline
include/linux/highmem.h | 24 ++++++++++++++++++++++++
include/linux/mm.h | 5 ++++-
mm/memory.c | 33 +++++++++++++++++++++++----------
3 files changed, 51 insertions(+), 11 deletions(-)
--
2.18.4
next reply other threads:[~2023-06-26 23:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-26 23:02 Jane Chu [this message]
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 ` [5.15/6.1-stable PATCH] Copy-on-write hwpoison recovery Greg KH
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=20230626230221.3064291-1-jane.chu@oracle.com \
--to=jane.chu@oracle.com \
--cc=dan.j.williams@intel.com \
--cc=glider@google.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