From: David Hildenbrand <david@redhat.com>
To: Miaohe Lin <linmiaohe@huawei.com>, akpm@linux-foundation.org
Cc: willy@infradead.org, vbabka@suse.cz, dhowells@redhat.com,
neilb@suse.de, apopple@nvidia.com, surenb@google.com,
minchan@kernel.org, peterx@redhat.com, sfr@canb.auug.org.au,
naoya.horiguchi@nec.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/3] mm/swapfile: Fix lost swap bits in unuse_pte()
Date: Mon, 25 Apr 2022 09:39:09 +0200 [thread overview]
Message-ID: <fcf69d7c-dded-666c-def1-4ce9f58ed852@redhat.com> (raw)
In-Reply-To: <20220424091105.48374-3-linmiaohe@huawei.com>
On 24.04.22 11:11, Miaohe Lin wrote:
> This is observed by code review only but not any real report.
>
> When we turn off swapping we could have lost the bits stored in the swap
> ptes. The new rmap-exclusive bit is fine since that turned into a page
> flag, but not for soft-dirty and uffd-wp. Add them.
>
> Suggested-by: Peter Xu <peterx@redhat.com>
> Signed-off-by: Miaohe Lin <linmiaohe@huawei.com>
> ---
> mm/swapfile.c | 10 +++++++---
> 1 file changed, 7 insertions(+), 3 deletions(-)
>
> diff --git a/mm/swapfile.c b/mm/swapfile.c
> index 95b63f69f388..522a0eb16bf1 100644
> --- a/mm/swapfile.c
> +++ b/mm/swapfile.c
> @@ -1783,7 +1783,7 @@ static int unuse_pte(struct vm_area_struct *vma, pmd_t *pmd,
> {
> struct page *swapcache;
> spinlock_t *ptl;
> - pte_t *pte;
> + pte_t *pte, new_pte;
> int ret = 1;
>
> swapcache = page;
> @@ -1832,8 +1832,12 @@ static int unuse_pte(struct vm_area_struct *vma, pmd_t *pmd,
> page_add_new_anon_rmap(page, vma, addr);
> lru_cache_add_inactive_or_unevictable(page, vma);
> }
> - set_pte_at(vma->vm_mm, addr, pte,
> - pte_mkold(mk_pte(page, vma->vm_page_prot)));
> + new_pte = pte_mkold(mk_pte(page, vma->vm_page_prot));
> + if (pte_swp_soft_dirty(*pte))
> + new_pte = pte_mksoft_dirty(new_pte);
> + if (pte_swp_uffd_wp(*pte))
> + new_pte = pte_mkuffd_wp(new_pte);
> + set_pte_at(vma->vm_mm, addr, pte, new_pte);
> swap_free(entry);
> out:
> pte_unmap_unlock(pte, ptl);
Reviewed-by: David Hildenbrand <david@redhat.com>
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2022-04-25 7:39 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-24 9:11 [PATCH v3 0/3] A few fixup patches for mm Miaohe Lin
2022-04-24 9:11 ` [PATCH v3 1/3] mm/swapfile: unuse_pte can map random data if swap read fails Miaohe Lin
2022-04-25 1:08 ` HORIGUCHI NAOYA(堀口 直也)
2022-04-25 2:20 ` Miaohe Lin
2022-04-25 2:51 ` HORIGUCHI NAOYA(堀口 直也)
2022-04-25 3:10 ` Miaohe Lin
2022-04-25 7:45 ` David Hildenbrand
2022-04-25 8:47 ` Miaohe Lin
2022-04-26 0:31 ` HORIGUCHI NAOYA(堀口 直也)
2022-04-26 7:06 ` Miaohe Lin
2022-04-25 7:41 ` ying.huang
2022-04-25 7:49 ` David Hildenbrand
2022-04-25 7:55 ` ying.huang
2022-04-25 8:01 ` David Hildenbrand
2022-04-25 8:51 ` Miaohe Lin
2022-05-10 6:17 ` HORIGUCHI NAOYA(堀口 直也)
2022-05-10 6:58 ` Miaohe Lin
2022-05-13 0:42 ` Andrew Morton
2022-05-13 3:14 ` Miaohe Lin
2022-05-10 12:46 ` Miaohe Lin
2022-04-24 9:11 ` [PATCH v3 2/3] mm/swapfile: Fix lost swap bits in unuse_pte() Miaohe Lin
2022-04-25 7:39 ` David Hildenbrand [this message]
2022-04-24 9:11 ` [PATCH v3 3/3] mm/madvise: free hwpoison and swapin error entry in madvise_free_pte_range Miaohe Lin
2022-04-24 23:41 ` HORIGUCHI NAOYA(堀口 直也)
2022-04-25 1:59 ` Miaohe Lin
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=fcf69d7c-dded-666c-def1-4ce9f58ed852@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=apopple@nvidia.com \
--cc=dhowells@redhat.com \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=naoya.horiguchi@nec.com \
--cc=neilb@suse.de \
--cc=peterx@redhat.com \
--cc=sfr@canb.auug.org.au \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
--cc=willy@infradead.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