stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yang Shi <shy828301@gmail.com>
To: Mike Kravetz <mike.kravetz@oracle.com>
Cc: "HORIGUCHI NAOYA(堀口 直也)" <naoya.horiguchi@nec.com>,
	"Naoya Horiguchi" <naoya.horiguchi@linux.dev>,
	"Greg KH" <gregkh@linuxfoundation.org>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>,
	"James Houghton" <jthoughton@google.com>,
	"Muchun Song" <songmuchun@bytedance.com>,
	"Miaohe Lin" <linmiaohe@huawei.com>,
	"Andrew Morton" <akpm@linux-foundation.org>
Subject: Re: hwpoison, shmem: fix data lost issue for 5.15.y
Date: Wed, 23 Nov 2022 10:54:15 -0800	[thread overview]
Message-ID: <CAHbLzkqhewJ27Er-nuhm18oSZtFxb0BE4a-SvGoZsc5M6+=yxQ@mail.gmail.com> (raw)
In-Reply-To: <Y31xw1DcqXGx86Fz@monkey>

On Tue, Nov 22, 2022 at 5:05 PM Mike Kravetz <mike.kravetz@oracle.com> wrote:
>
> On 11/15/22 01:16, HORIGUCHI NAOYA(堀口 直也) wrote:
> > On Mon, Nov 14, 2022 at 02:53:51PM -0800, Mike Kravetz wrote:
> > > On 11/15/22 07:39, Naoya Horiguchi wrote:
> > > > On Mon, Nov 14, 2022 at 05:11:35PM +0100, Greg KH wrote:
> > > > > On Mon, Nov 14, 2022 at 10:14:03PM +0900, Naoya Horiguchi wrote:
> > > > > > Hi,
> > > > > >
> > > > > > I'd like to request the follow commits to be backported to 5.15.y.
> > > > > >
> > > > > > - dd0f230a0a80 ("mm: hwpoison: refactor refcount check handling")
> > > > > > - 4966455d9100 ("mm: hwpoison: handle non-anonymous THP correctly")
> > > > > > - a76054266661 ("mm: shmem: don't truncate page if memory failure happens")
> > > > > >
> > > > > > These patches fixed a data lost issue by preventing shmem pagecache from
> > > > > > being removed by memory error.  These were not tagged for stable originally,
> > > > > > but that's revisited recently.
> > > > >
> > > > > And have you tested that these all apply properly (and in which order?)
> > > >
> > > > Yes, I've checked that these cleanly apply (without any change) on
> > > > 5.15.78 in the above order (i.e. dd0f23 is first, 496645 comes next,
> > > > then a76054).
> > > >
> > > > > and work correctly?
> > > >
> > > > Yes, I ran related testcases in my test suite, and their status changed
> > > > FAIL to PASS with these patches.
> > >
> > > Hi Naoya,
> > >
> > > Just curious if you have plans to do backports for earlier releases?
> >
> > I didn't have a clear plan.  I just thought that we should backport to
> > earlier kernels if someone want and the patches are applicable easily
> > enough and well-tested.
> >
> > >
> > > If not, I can start that effort.  We have seen data loss/corruption because of
> > > this on a 4.14 based release.   So, I would go at least that far back.
> >
> > Thank you for raising hand, that's really helpful.
> >
> > Maybe dd0f230a0a80 ("[PATCH] hugetlbfs: don't delete error page from
> > pagecbache") should be considered to backport together, because it's
> > the similar issue and reported (a while ago) to fail to backport.
> > dd0f230a0a80 does not apply cleanly on top of 5.15.78 + the above 3 patches.
> > So I need check more and will update my current proposal for 5.15.y.
>
> When working with 5.10.y, I noticed that commit eac96c3efdb5 ("mm: filemap:
> check if THP has hwpoisoned subpage for PMD page fault") as well as the
> prereq commit c7cb42e94473 ("mm: hwpoison: remove the unnecessary THP check")
> were not backported to 5.10.y.  Without those patches, THP testing will
> fail.
>
> Naoya and Yang Shi, does that sound right?

Yes, since the hwpoisoned THP will be kept in page cache so the page
fault may happen on it again, without that commit the page fault won't
return -EHWPOISON if I remember correctly.

>
> I have backports for those as well but want to check if you think
> anything else is needed.

Thanks for backporting them. No more fix is needed AFAICT.

> --
> Mike Kravetz

  reply	other threads:[~2022-11-23 18:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-14 13:14 hwpoison, shmem: fix data lost issue for 5.15.y Naoya Horiguchi
2022-11-14 16:11 ` Greg KH
2022-11-14 22:39   ` Naoya Horiguchi
2022-11-14 22:53     ` Mike Kravetz
2022-11-15  1:16       ` HORIGUCHI NAOYA(堀口 直也)
2022-11-15  1:30         ` Mike Kravetz
2022-11-15  6:39           ` Naoya Horiguchi
2022-11-16  3:48             ` Mike Kravetz
2022-11-16 23:58               ` Naoya Horiguchi
2022-11-23  1:05         ` Mike Kravetz
2022-11-23 18:54           ` Yang Shi [this message]
2022-11-24  3:03             ` Naoya Horiguchi
2022-11-16  9:16     ` 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='CAHbLzkqhewJ27Er-nuhm18oSZtFxb0BE4a-SvGoZsc5M6+=yxQ@mail.gmail.com' \
    --to=shy828301@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jthoughton@google.com \
    --cc=linmiaohe@huawei.com \
    --cc=mike.kravetz@oracle.com \
    --cc=naoya.horiguchi@linux.dev \
    --cc=naoya.horiguchi@nec.com \
    --cc=songmuchun@bytedance.com \
    --cc=stable@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).