From: Suren Baghdasaryan <surenb@google.com>
To: Ryan Roberts <ryan.roberts@arm.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Andrea Arcangeli <aarcange@redhat.com>,
linux-mm@kvack.org
Subject: Re: [PATCH v1] mm/userfaultfd: UFFDIO_MOVE implementation should use ptep_get()
Date: Tue, 23 Jan 2024 12:54:32 -0800 [thread overview]
Message-ID: <CAJuCfpHSibd+zn2kM5ZWiCKMgBJs0aG01t+10Td=VEJVG41tRA@mail.gmail.com> (raw)
In-Reply-To: <20240123141755.3836179-1-ryan.roberts@arm.com>
On Tue, Jan 23, 2024 at 6:18 AM Ryan Roberts <ryan.roberts@arm.com> wrote:
>
> Commit c33c794828f2 ("mm: ptep_get() conversion") converted all
> (non-arch) call sites to use ptep_get() instead of doing a direct
> dereference of the pte. Full rationale can be found in that commit's
> log.
>
> Since then, UFFDIO_MOVE has been implemented which does 7 direct pte
> dereferences. Let's fix those up to use ptep_get().
>
> Fixes: adef440691ba ("userfaultfd: UFFDIO_MOVE uABI")
> Signed-off-by: Ryan Roberts <ryan.roberts@arm.com>
Looks like it does convert all instances introduced by UFFDIO_MOVE
patch. Thanks!
Reviewed-by: Suren Baghdasaryan <surenb@google.com>
> ---
> Hi All,
>
> This applies on top of v6.8-rc1. I'm hoping this can be merged into the
> next rc.
>
> I've asserted in the past that there is no reliable automated mechanism
> to catch these; I'm relying on a combination of Coccinelle (which throws
> up a lot of false positives) and some compiler magic to force a compiler
> error on dereference. But given the frequency with which new issues are
> coming up, I'll add it to my todo list to try to find an automated
> solution.
>
> Thanks,
> Ryan
>
> mm/userfaultfd.c | 14 +++++++-------
> 1 file changed, 7 insertions(+), 7 deletions(-)
>
> diff --git a/mm/userfaultfd.c b/mm/userfaultfd.c
> index 20e3b0d9cf7e..aaa7b9821342 100644
> --- a/mm/userfaultfd.c
> +++ b/mm/userfaultfd.c
> @@ -891,8 +891,8 @@ static int move_present_pte(struct mm_struct *mm,
>
> double_pt_lock(dst_ptl, src_ptl);
>
> - if (!pte_same(*src_pte, orig_src_pte) ||
> - !pte_same(*dst_pte, orig_dst_pte)) {
> + if (!pte_same(ptep_get(src_pte), orig_src_pte) ||
> + !pte_same(ptep_get(dst_pte), orig_dst_pte)) {
> err = -EAGAIN;
> goto out;
> }
> @@ -935,8 +935,8 @@ static int move_swap_pte(struct mm_struct *mm,
>
> double_pt_lock(dst_ptl, src_ptl);
>
> - if (!pte_same(*src_pte, orig_src_pte) ||
> - !pte_same(*dst_pte, orig_dst_pte)) {
> + if (!pte_same(ptep_get(src_pte), orig_src_pte) ||
> + !pte_same(ptep_get(dst_pte), orig_dst_pte)) {
> double_pt_unlock(dst_ptl, src_ptl);
> return -EAGAIN;
> }
> @@ -1005,7 +1005,7 @@ static int move_pages_pte(struct mm_struct *mm, pmd_t *dst_pmd, pmd_t *src_pmd,
> }
>
> spin_lock(dst_ptl);
> - orig_dst_pte = *dst_pte;
> + orig_dst_pte = ptep_get(dst_pte);
> spin_unlock(dst_ptl);
> if (!pte_none(orig_dst_pte)) {
> err = -EEXIST;
> @@ -1013,7 +1013,7 @@ static int move_pages_pte(struct mm_struct *mm, pmd_t *dst_pmd, pmd_t *src_pmd,
> }
>
> spin_lock(src_ptl);
> - orig_src_pte = *src_pte;
> + orig_src_pte = ptep_get(src_pte);
> spin_unlock(src_ptl);
> if (pte_none(orig_src_pte)) {
> if (!(mode & UFFDIO_MOVE_MODE_ALLOW_SRC_HOLES))
> @@ -1043,7 +1043,7 @@ static int move_pages_pte(struct mm_struct *mm, pmd_t *dst_pmd, pmd_t *src_pmd,
> * page isn't freed under us
> */
> spin_lock(src_ptl);
> - if (!pte_same(orig_src_pte, *src_pte)) {
> + if (!pte_same(orig_src_pte, ptep_get(src_pte))) {
> spin_unlock(src_ptl);
> err = -EAGAIN;
> goto out;
> --
> 2.25.1
>
next prev parent reply other threads:[~2024-01-23 20:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-23 14:17 [PATCH v1] mm/userfaultfd: UFFDIO_MOVE implementation should use ptep_get() Ryan Roberts
2024-01-23 20:54 ` Suren Baghdasaryan [this message]
2024-01-24 13:57 ` David Hildenbrand
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='CAJuCfpHSibd+zn2kM5ZWiCKMgBJs0aG01t+10Td=VEJVG41tRA@mail.gmail.com' \
--to=surenb@google.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=ryan.roberts@arm.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;
as well as URLs for NNTP newsgroup(s).