linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Barry Song <21cnbao@gmail.com>
To: Peter Xu <peterx@redhat.com>
Cc: linux-mm@kvack.org, akpm@linux-foundation.org,
	 linux-kernel@vger.kernel.org, zhengtangquan@oppo.com,
	 Barry Song <v-songbaohua@oppo.com>,
	Andrea Arcangeli <aarcange@redhat.com>,
	 Suren Baghdasaryan <surenb@google.com>,
	Al Viro <viro@zeniv.linux.org.uk>,
	 Axel Rasmussen <axelrasmussen@google.com>,
	Brian Geffon <bgeffon@google.com>,
	 Christian Brauner <brauner@kernel.org>,
	David Hildenbrand <david@redhat.com>,
	Hugh Dickins <hughd@google.com>,  Jann Horn <jannh@google.com>,
	Kalesh Singh <kaleshsingh@google.com>,
	 "Liam R . Howlett" <Liam.Howlett@oracle.com>,
	Lokesh Gidra <lokeshgidra@google.com>,
	 Matthew Wilcox <willy@infradead.org>,
	Michal Hocko <mhocko@suse.com>, Mike Rapoport <rppt@kernel.org>,
	 Nicolas Geoffray <ngeoffray@google.com>,
	Ryan Roberts <ryan.roberts@arm.com>,
	 Shuah Khan <shuah@kernel.org>,
	ZhangPeng <zhangpeng362@huawei.com>
Subject: Re: [PATCH RFC] mm: Fix kernel BUG when userfaultfd_move encounters swapcache
Date: Thu, 20 Feb 2025 13:50:23 +1300	[thread overview]
Message-ID: <CAGsJ_4xDX5QFNemckan6FoeEoA8tU75HyX+viVdec2b0qLbPYg@mail.gmail.com> (raw)
In-Reply-To: <Z7Zbz7_39JZgdLYa@x1.local>

On Thu, Feb 20, 2025 at 11:31 AM Peter Xu <peterx@redhat.com> wrote:
>
> On Thu, Feb 20, 2025 at 12:25:19AM +1300, Barry Song wrote:
> > @@ -1079,9 +1080,19 @@ static int move_swap_pte(struct mm_struct *mm,
> >                        pmd_t *dst_pmd, pmd_t dst_pmdval,
> >                        spinlock_t *dst_ptl, spinlock_t *src_ptl)
> >  {
> > +     struct folio *folio;
> > +     swp_entry_t entry;
> > +
> >       if (!pte_swp_exclusive(orig_src_pte))
> >               return -EBUSY;
> >
> > +     entry = pte_to_swp_entry(orig_src_pte);
> > +     folio = filemap_get_folio(swap_address_space(entry), swap_cache_index(entry));
>
> [Besides what's being discussed elsewhere..]
>
> swap_cache_get_folio() says:
>
>  * Caller must lock the swap device or hold a reference to keep it valid.
>
> Do we need get_swap_device() too here to avoid swapoff race?
>

Yep, thanks! Let me fix it in v2.

> > +     if (!IS_ERR(folio)) {
> > +             folio_put(folio);
> > +             return -EBUSY;
> > +     }
> > +
> >       double_pt_lock(dst_ptl, src_ptl);
> >
> >       if (!is_pte_pages_stable(dst_pte, src_pte, orig_dst_pte, orig_src_pte,
> > --
> > 2.39.3 (Apple Git-146)
> >
>
> --
> Peter Xu
>

Thanks
Barry


      reply	other threads:[~2025-02-20  0:50 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-19 11:25 Barry Song
2025-02-19 18:26 ` Suren Baghdasaryan
2025-02-19 18:30   ` David Hildenbrand
2025-02-19 18:58     ` Suren Baghdasaryan
2025-02-20  8:40       ` David Hildenbrand
2025-02-20  9:21         ` Barry Song
2025-02-20 10:24           ` David Hildenbrand
2025-02-26  5:37             ` Barry Song
2025-02-26  8:03               ` David Hildenbrand
2025-02-20 23:32           ` Peter Xu
2025-02-21  0:07             ` Barry Song
2025-02-21  1:49               ` Peter Xu
2025-02-22 21:31                 ` Barry Song
2025-02-24 17:50                   ` Peter Xu
2025-02-24 18:03                     ` David Hildenbrand
2025-02-19 20:37   ` Barry Song
2025-02-19 20:57     ` Matthew Wilcox
2025-02-19 21:05       ` Barry Song
2025-02-19 21:02     ` Lokesh Gidra
2025-02-19 21:26       ` Barry Song
2025-02-19 21:32         ` Lokesh Gidra
2025-02-19 22:14     ` Peter Xu
2025-02-19 23:04       ` Barry Song
2025-02-19 23:19         ` Lokesh Gidra
2025-02-20  0:49           ` Barry Song
2025-02-20 22:59         ` Peter Xu
2025-02-20 23:47           ` Suren Baghdasaryan
2025-02-20 23:52             ` Suren Baghdasaryan
2025-02-21  0:36               ` Suren Baghdasaryan
2025-02-25 11:05                 ` Barry Song
2025-02-25 15:34                   ` Peter Xu
2025-02-25 17:02                     ` Suren Baghdasaryan
2025-02-21  1:36           ` Barry Song
2025-02-21  1:54             ` Peter Xu
2025-02-20  8:51     ` David Hildenbrand
2025-02-20  9:31       ` Barry Song
2025-02-20  9:36         ` David Hildenbrand
2025-02-20 21:45           ` Barry Song
2025-02-20 22:19             ` Lokesh Gidra
2025-02-20 22:26               ` Barry Song
2025-02-20 22:31                 ` David Hildenbrand
2025-02-20 22:33                 ` Lokesh Gidra
2025-02-19 18:40 ` Lokesh Gidra
2025-02-19 20:45   ` Barry Song
2025-02-19 20:53     ` Lokesh Gidra
2025-02-19 22:31 ` Peter Xu
2025-02-20  0:50   ` Barry Song [this message]

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=CAGsJ_4xDX5QFNemckan6FoeEoA8tU75HyX+viVdec2b0qLbPYg@mail.gmail.com \
    --to=21cnbao@gmail.com \
    --cc=Liam.Howlett@oracle.com \
    --cc=aarcange@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=axelrasmussen@google.com \
    --cc=bgeffon@google.com \
    --cc=brauner@kernel.org \
    --cc=david@redhat.com \
    --cc=hughd@google.com \
    --cc=jannh@google.com \
    --cc=kaleshsingh@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lokeshgidra@google.com \
    --cc=mhocko@suse.com \
    --cc=ngeoffray@google.com \
    --cc=peterx@redhat.com \
    --cc=rppt@kernel.org \
    --cc=ryan.roberts@arm.com \
    --cc=shuah@kernel.org \
    --cc=surenb@google.com \
    --cc=v-songbaohua@oppo.com \
    --cc=viro@zeniv.linux.org.uk \
    --cc=willy@infradead.org \
    --cc=zhangpeng362@huawei.com \
    --cc=zhengtangquan@oppo.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