From: David Hildenbrand <david@redhat.com>
To: Qi Zheng <zhengqi.arch@bytedance.com>,
hughd@google.com, willy@infradead.org, muchun.song@linux.dev,
vbabka@kernel.org, akpm@linux-foundation.org, rppt@kernel.org,
vishal.moola@gmail.com, peterx@redhat.com, ryan.roberts@arm.com,
christophe.leroy2@cs-soprasteria.com
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-arm-kernel@lists.infradead.org,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v2 02/14] arm: adjust_pte() use pte_offset_map_rw_nolock()
Date: Mon, 26 Aug 2024 17:26:55 +0200 [thread overview]
Message-ID: <77f3f5ce-dd12-4ca2-90cd-0f2226fe26ba@redhat.com> (raw)
In-Reply-To: <7915acf5887e7bf0c5cc71ff30ad2fe8447d005d.1724310149.git.zhengqi.arch@bytedance.com>
On 22.08.24 09:13, Qi Zheng wrote:
> In do_adjust_pte(), we may modify the pte entry. At this time, the write
> lock of mmap_lock is not held, and the pte_same() check is not performed
> after the PTL held. The corresponding pmd entry may have been modified
> concurrently. Therefore, in order to ensure the stability if pmd entry,
> use pte_offset_map_rw_nolock() to replace pte_offset_map_nolock(), and do
> pmd_same() check after holding the PTL.
>
> Signed-off-by: Qi Zheng <zhengqi.arch@bytedance.com>
> ---
> arch/arm/mm/fault-armv.c | 9 ++++++++-
> 1 file changed, 8 insertions(+), 1 deletion(-)
>
> diff --git a/arch/arm/mm/fault-armv.c b/arch/arm/mm/fault-armv.c
> index 831793cd6ff94..de6c7d8a2ddfc 100644
> --- a/arch/arm/mm/fault-armv.c
> +++ b/arch/arm/mm/fault-armv.c
> @@ -94,6 +94,7 @@ static int adjust_pte(struct vm_area_struct *vma, unsigned long address,
> pud_t *pud;
> pmd_t *pmd;
> pte_t *pte;
> + pmd_t pmdval;
> int ret;
>
> pgd = pgd_offset(vma->vm_mm, address);
> @@ -112,16 +113,22 @@ static int adjust_pte(struct vm_area_struct *vma, unsigned long address,
> if (pmd_none_or_clear_bad(pmd))
> return 0;
>
> +again:
> /*
> * This is called while another page table is mapped, so we
> * must use the nested version. This also means we need to
> * open-code the spin-locking.
> */
> - pte = pte_offset_map_nolock(vma->vm_mm, pmd, address, &ptl);
> + pte = pte_offset_map_rw_nolock(vma->vm_mm, pmd, address, &pmdval, &ptl);
> if (!pte)
> return 0;
>
> do_pte_lock(ptl);
> + if (unlikely(!pmd_same(pmdval, pmdp_get_lockless(pmd)))) {
> + do_pte_unlock(ptl);
> + pte_unmap(pte);
> + goto again;
> + }
>
> ret = do_adjust_pte(vma, address, pfn, pte);
>
Looks correct to me, but I wonder why the missing pmd_same check is not
an issue so far ... any experts? THP on __LINUX_ARM_ARCH__ < 6 is not
really used/possible?
Acked-by: David Hildenbrand <david@redhat.com>
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2024-08-26 15:27 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-22 7:13 [PATCH v2 00/14] introduce pte_offset_map_{ro|rw}_nolock() Qi Zheng
2024-08-22 7:13 ` [PATCH v2 01/14] mm: pgtable: " Qi Zheng
2024-08-26 3:45 ` [PATCH v2 01/14 update] " Qi Zheng
2024-08-26 15:21 ` [PATCH v2 01/14] " David Hildenbrand
2024-08-27 4:33 ` Qi Zheng
2024-08-28 10:48 ` David Hildenbrand
2024-08-29 3:27 ` Qi Zheng
2024-08-29 10:59 ` Qi Zheng
2024-08-29 15:31 ` David Hildenbrand
2024-08-30 6:37 ` Qi Zheng
2024-08-28 9:48 ` Muchun Song
2024-08-22 7:13 ` [PATCH v2 02/14] arm: adjust_pte() use pte_offset_map_rw_nolock() Qi Zheng
2024-08-26 15:26 ` David Hildenbrand [this message]
2024-08-29 3:39 ` Muchun Song
2024-08-22 7:13 ` [PATCH v2 03/14] powerpc: assert_pte_locked() use pte_offset_map_ro_nolock() Qi Zheng
2024-08-26 15:28 ` David Hildenbrand
2024-08-29 7:21 ` Muchun Song
2024-08-22 7:13 ` [PATCH v2 04/14] mm: filemap: filemap_fault_recheck_pte_none() " Qi Zheng
2024-08-26 15:29 ` David Hildenbrand
2024-08-29 7:23 ` Muchun Song
2024-08-22 7:13 ` [PATCH v2 05/14] mm: khugepaged: __collapse_huge_page_swapin() " Qi Zheng
2024-08-26 15:33 ` David Hildenbrand
2024-08-29 7:25 ` Muchun Song
2024-08-22 7:13 ` [PATCH v2 06/14] mm: handle_pte_fault() use pte_offset_map_rw_nolock() Qi Zheng
2024-08-26 15:36 ` David Hildenbrand
2024-08-27 4:53 ` Qi Zheng
2024-08-29 7:30 ` Muchun Song
2024-08-22 7:13 ` [PATCH v2 07/14] mm: khugepaged: collapse_pte_mapped_thp() " Qi Zheng
2024-08-29 8:10 ` Muchun Song
2024-08-30 6:54 ` Qi Zheng
2024-09-05 6:32 ` Muchun Song
2024-09-05 6:41 ` Qi Zheng
2024-09-05 7:18 ` Muchun Song
2024-08-22 7:13 ` [PATCH v2 08/14] mm: copy_pte_range() " Qi Zheng
2024-08-29 8:13 ` Muchun Song
2024-08-29 15:36 ` David Hildenbrand
2024-08-30 6:42 ` Qi Zheng
2024-08-22 7:13 ` [PATCH v2 09/14] mm: mremap: move_ptes() " Qi Zheng
2024-08-22 7:13 ` [PATCH v2 10/14] mm: page_vma_mapped_walk: map_pte() " Qi Zheng
2024-08-22 7:13 ` [PATCH v2 11/14] mm: userfaultfd: move_pages_pte() " Qi Zheng
2024-08-22 7:13 ` [PATCH v2 12/14] mm: multi-gen LRU: walk_pte_range() " Qi Zheng
2024-08-22 7:13 ` [PATCH v2 13/14] mm: pgtable: remove pte_offset_map_nolock() Qi Zheng
2024-08-22 7:13 ` [PATCH v2 14/14] mm: khugepaged: retract_page_tables() use pte_offset_map_rw_nolock() Qi Zheng
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=77f3f5ce-dd12-4ca2-90cd-0f2226fe26ba@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=christophe.leroy2@cs-soprasteria.com \
--cc=hughd@google.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=muchun.song@linux.dev \
--cc=peterx@redhat.com \
--cc=rppt@kernel.org \
--cc=ryan.roberts@arm.com \
--cc=vbabka@kernel.org \
--cc=vishal.moola@gmail.com \
--cc=willy@infradead.org \
--cc=zhengqi.arch@bytedance.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