linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Charan Teja Kalla <quic_charante@quicinc.com>
To: Zi Yan <ziy@nvidia.com>, <gregkh@linuxfoundation.org>,
	<stable@vger.kernel.org>
Cc: <linux-mm@kvack.org>,
	"Matthew Wilcox (Oracle)" <willy@infradead.org>,
	David Hildenbrand <david@redhat.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Huang Ying <ying.huang@intel.com>,
	Naoya Horiguchi <naoya.horiguchi@linux.dev>
Subject: Re: [PATCH STABLE v6.1.y] mm/migrate: set swap entry values of THP tail pages properly.
Date: Wed, 13 Mar 2024 16:53:10 +0530	[thread overview]
Message-ID: <8dd12cfc-e5bd-caae-5a32-e1203a478bac@quicinc.com> (raw)
In-Reply-To: <20240306155217.118467-1-zi.yan@sent.com>


On 3/6/2024 9:22 PM, Zi Yan wrote:
> From: Zi Yan <ziy@nvidia.com>
> 
> The tail pages in a THP can have swap entry information stored in their
> private field. When migrating to a new page, all tail pages of the new
> page need to update ->private to avoid future data corruption.
> 
> This fix is stable-only, since after commit 07e09c483cbe ("mm/huge_memory:
> work on folio->swap instead of page->private when splitting folio"),
> subpages of a swapcached THP no longer requires the maintenance.
> 
> Adding THPs to the swapcache was introduced in commit
> 38d8b4e6bdc87 ("mm, THP, swap: delay splitting THP during swap out"),
> where each subpage of a THP added to the swapcache had its own swapcache
> entry and required the ->private field to point to the correct swapcache
> entry. Later, when THP migration functionality was implemented in commit
> 616b8371539a6 ("mm: thp: enable thp migration in generic path"),
> it initially did not handle the subpages of swapcached THPs, failing to
> update their ->private fields or replace the subpage pointers in the
> swapcache. Subsequently, commit e71769ae5260 ("mm: enable thp migration
> for shmem thp") addressed the swapcache update aspect. This patch fixes
> the update of subpage ->private fields.
> 
> Closes: https://lore.kernel.org/linux-mm/1707814102-22682-1-git-send-email-quic_charante@quicinc.com/
> Fixes: 616b8371539a ("mm: thp: enable thp migration in generic path")
> Signed-off-by: Zi Yan <ziy@nvidia.com>
> Acked-by: David Hildenbrand <david@redhat.com>

Tested this patch for 6.1 kernel and observed no issues. With that,

Reported-and-tested-by: Charan Teja Kalla <quic_charante@quicinc.com>

Thanks,
Charan


  reply	other threads:[~2024-03-13 11:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-06 15:52 Zi Yan
2024-03-13 11:23 ` Charan Teja Kalla [this message]
2024-03-30  9:20 ` Patch "mm/migrate: set swap entry values of THP tail pages properly." has been added to the 6.1-stable tree gregkh
  -- strict thread matches above, loose matches on Subject: below --
2024-03-05 16:13 [PATCH STABLE v6.1.y] mm/migrate: set swap entry values of THP tail pages properly Zi Yan
2024-03-05 16:17 ` Zi Yan
2024-03-05 16:22   ` Charan Teja Kalla
2024-03-05 16:26     ` Zi Yan
2024-03-05 16:22 ` David Hildenbrand
2024-03-05 22:04 ` Greg KH
2024-03-05 22:09   ` David Hildenbrand
2024-03-05 22:32     ` Greg KH
2024-03-05 23:13       ` Zi Yan
2024-03-06 13:51         ` 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=8dd12cfc-e5bd-caae-5a32-e1203a478bac@quicinc.com \
    --to=quic_charante@quicinc.com \
    --cc=akpm@linux-foundation.org \
    --cc=david@redhat.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-mm@kvack.org \
    --cc=naoya.horiguchi@linux.dev \
    --cc=stable@vger.kernel.org \
    --cc=willy@infradead.org \
    --cc=ying.huang@intel.com \
    --cc=ziy@nvidia.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