Linux kernel -stable discussions
 help / color / mirror / Atom feed
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-stable PATCH 0/2] Copy-on-write hwpoison recovery
Date: Mon, 19 Jun 2023 10:28:17 +0200	[thread overview]
Message-ID: <2023061926-copied-glowworm-8cee@gregkh> (raw)
In-Reply-To: <20230615015255.1260473-1-jane.chu@oracle.com>

On Wed, Jun 14, 2023 at 07:52:53PM -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.

But you are skipping 6.1.y, which is not ok as it would cause
regressions when you upgrade.

I'll drop this from my review queue now, please provide working
backports for this and newer releases, and I'll be glad to take them.

thanks,

greg k-h

  parent reply	other threads:[~2023-06-19  8:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-15  1:52 [5.15-stable PATCH 0/2] Copy-on-write hwpoison recovery Jane Chu
2023-06-15  1:52 ` [5.15-stable PATCH 1/2] mm, hwpoison: try to recover from copy-on write faults Jane Chu
2023-06-15  1:52 ` [5.15-stable PATCH 2/2] mm, hwpoison: when copy-on-write hits poison, take page offline Jane Chu
2023-06-19  8:28 ` Greg KH [this message]
2023-06-20 18:36   ` [5.15-stable PATCH 0/2] Copy-on-write hwpoison recovery Jane Chu
2023-06-20 18:42     ` Greg KH
2023-06-20 19:50       ` Jane Chu

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=2023061926-copied-glowworm-8cee@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