linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Zi Yan <ziy@nvidia.com>
To: gregkh@linuxfoundation.org, stable@vger.kernel.org
Cc: Zi Yan <ziy@nvidia.com>,
	linux-mm@kvack.org, Charan Teja Kalla <quic_charante@quicinc.com>,
	"\"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: Tue, 05 Mar 2024 11:17:30 -0500	[thread overview]
Message-ID: <F242A2B9-8791-4446-A35D-110A77919115@nvidia.com> (raw)
In-Reply-To: <20240305161313.90954-1-zi.yan@sent.com>

[-- Attachment #1: Type: text/plain, Size: 1305 bytes --]

On 5 Mar 2024, at 11:13, 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.

Corresponding swapcache entries need to be updated as well.
e71769ae5260 ("mm: enable thp migration for shmem thp") fixed it already.

Fixes: 616b8371539a ("mm: thp: enable thp migration in generic path")


>
> Signed-off-by: Zi Yan <ziy@nvidia.com>
> ---
>  mm/migrate.c | 6 +++++-
>  1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/mm/migrate.c b/mm/migrate.c
> index c93dd6a31c31..c5968021fde0 100644
> --- a/mm/migrate.c
> +++ b/mm/migrate.c
> @@ -423,8 +423,12 @@ int folio_migrate_mapping(struct address_space *mapping,
>  	if (folio_test_swapbacked(folio)) {
>  		__folio_set_swapbacked(newfolio);
>  		if (folio_test_swapcache(folio)) {
> +			int i;
> +
>  			folio_set_swapcache(newfolio);
> -			newfolio->private = folio_get_private(folio);
> +			for (i = 0; i < nr; i++)
> +				set_page_private(folio_page(newfolio, i),
> +					page_private(folio_page(folio, i)));
>  		}
>  		entries = nr;
>  	} else {
> -- 
> 2.43.0


--
Best Regards,
Yan, Zi

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 854 bytes --]

  reply	other threads:[~2024-03-05 16:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-05 16:13 Zi Yan
2024-03-05 16:17 ` Zi Yan [this message]
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
2024-03-06 15:52 Zi Yan
2024-03-13 11:23 ` Charan Teja Kalla

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=F242A2B9-8791-4446-A35D-110A77919115@nvidia.com \
    --to=ziy@nvidia.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=quic_charante@quicinc.com \
    --cc=stable@vger.kernel.org \
    --cc=willy@infradead.org \
    --cc=ying.huang@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