From: Miaohe Lin <linmiaohe@huawei.com>
To: David Hildenbrand <david@redhat.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 v2 2/3] mm/swapfile: Fix lost swap bits in unuse_pte()
Date: Thu, 21 Apr 2022 21:50:38 +0800 [thread overview]
Message-ID: <58980370-f1b6-afa9-9abb-1335bf369155@huawei.com> (raw)
In-Reply-To: <67fc9368-0876-b931-14c2-ffa4dac35b6d@redhat.com>
On 2022/4/21 21:13, David Hildenbrand wrote:
> On 21.04.22 14:53, 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 | 12 +++++++++---
>> 1 file changed, 9 insertions(+), 3 deletions(-)
>>
>> diff --git a/mm/swapfile.c b/mm/swapfile.c
>> index 95b63f69f388..332ccfc76142 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,14 @@ 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);
>> + new_pte = pte_wrprotect(new_pte);
>
> The wrprotect shouldn't be necessary, we don't do a pte_mkwrite(). Note
> that in do_swap_page() we might have done a
> maybe_mkwrite(pte_mkdirty(pte)), which is why the pte_wrprotect() is
> required there.
You're so smart. I happened to be referring to the code in do_swap_page. ;)
Now I see why pte_wrprotect() is only required there. Will remove it in the
next verison when there is enough feedback. Many thanks!
>
next prev parent reply other threads:[~2022-04-21 13:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-21 12:53 [PATCH v2 0/3] A few fixup patches for mm Miaohe Lin
2022-04-21 12:53 ` [PATCH v2 1/3] mm/swapfile: unuse_pte can map random data if swap read fails Miaohe Lin
2022-04-21 12:53 ` [PATCH v2 2/3] mm/swapfile: Fix lost swap bits in unuse_pte() Miaohe Lin
2022-04-21 13:13 ` David Hildenbrand
2022-04-21 13:50 ` Miaohe Lin [this message]
2022-04-21 12:53 ` [PATCH v2 3/3] mm/madvise: free hwpoison and swapin error entry in madvise_free_pte_range Miaohe Lin
2022-04-21 13:25 ` David Hildenbrand
2022-04-21 13:44 ` Miaohe Lin
2022-04-21 14:28 ` Peter Xu
2022-04-22 2:47 ` Miaohe Lin
2022-04-22 2:52 ` Peter Xu
2022-04-22 3:15 ` 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=58980370-f1b6-afa9-9abb-1335bf369155@huawei.com \
--to=linmiaohe@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=apopple@nvidia.com \
--cc=david@redhat.com \
--cc=dhowells@redhat.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