From: "Huang, Ying" <ying.huang@intel.com>
To: David Hildenbrand <david@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Hugh Dickins <hughd@google.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Matthew Wilcox <willy@infradead.org>,
Michal Hocko <mhocko@suse.com>, Minchan Kim <minchan@kernel.org>,
Tim Chen <tim.c.chen@linux.intel.com>,
Yang Shi <shy828301@gmail.com>, Yu Zhao <yuzhao@google.com>
Subject: Re: [PATCH -V2 2/5] swap, __read_swap_cache_async(): enlarge get/put_swap_device protection range
Date: Tue, 23 May 2023 08:43:15 +0800 [thread overview]
Message-ID: <87wn0zyj18.fsf@yhuang6-desk2.ccr.corp.intel.com> (raw)
In-Reply-To: <653a4881-d17b-6d8e-8066-300c0497a702@redhat.com> (David Hildenbrand's message of "Mon, 22 May 2023 14:01:32 +0200")
David Hildenbrand <david@redhat.com> writes:
> On 22.05.23 09:09, Huang Ying wrote:
>> This makes the function a little easier to be understood because we
>> don't need to consider swapoff. And this makes it possible to remove
>> get/put_swap_device() calling in some functions called by
>> __read_swap_cache_async().
>> Signed-off-by: "Huang, Ying" <ying.huang@intel.com>
>> Cc: David Hildenbrand <david@redhat.com>
>> Cc: Hugh Dickins <hughd@google.com>
>> Cc: Johannes Weiner <hannes@cmpxchg.org>
>> Cc: Matthew Wilcox <willy@infradead.org>
>> Cc: Michal Hocko <mhocko@suse.com>
>> Cc: Minchan Kim <minchan@kernel.org>
>> Cc: Tim Chen <tim.c.chen@linux.intel.com>
>> Cc: Yang Shi <shy828301@gmail.com>
>> Cc: Yu Zhao <yuzhao@google.com>
>> ---
>> mm/swap_state.c | 33 ++++++++++++++++++++++-----------
>> 1 file changed, 22 insertions(+), 11 deletions(-)
>> diff --git a/mm/swap_state.c b/mm/swap_state.c
>> index b76a65ac28b3..a1028fe7214e 100644
>> --- a/mm/swap_state.c
>> +++ b/mm/swap_state.c
>> @@ -417,9 +417,13 @@ struct page *__read_swap_cache_async(swp_entry_t entry, gfp_t gfp_mask,
>> {
>> struct swap_info_struct *si;
>> struct folio *folio;
>> + struct page *page;
>> void *shadow = NULL;
>> *new_page_allocated = false;
>> + si = get_swap_device(entry);
>> + if (!si)
>> + return NULL;
>> for (;;) {
>> int err;
>> @@ -428,14 +432,12 @@ struct page *__read_swap_cache_async(swp_entry_t entry, gfp_t gfp_mask,
>> * called after swap_cache_get_folio() failed, re-calling
>> * that would confuse statistics.
>> */
>> - si = get_swap_device(entry);
>> - if (!si)
>> - return NULL;
>> folio = filemap_get_folio(swap_address_space(entry),
>> swp_offset(entry));
>> - put_swap_device(si);
>> - if (!IS_ERR(folio))
>> - return folio_file_page(folio, swp_offset(entry));
>> + if (!IS_ERR(folio)) {
>> + page = folio_file_page(folio, swp_offset(entry));
>> + goto got_page;
>> + }
>> /*
>> * Just skip read ahead for unused swap slot.
>> @@ -445,8 +447,8 @@ struct page *__read_swap_cache_async(swp_entry_t entry, gfp_t gfp_mask,
>> * as SWAP_HAS_CACHE. That's done in later part of code or
>> * else swap_off will be aborted if we return NULL.
>> */
>> - if (!__swp_swapcount(entry) && swap_slot_cache_enabled)
>> - return NULL;
>> + if (!swap_swapcount(si, entry) && swap_slot_cache_enabled)
>> + goto fail;
>> /*
>> * Get a new page to read into from swap. Allocate it now,
>> @@ -455,7 +457,7 @@ struct page *__read_swap_cache_async(swp_entry_t entry, gfp_t gfp_mask,
>> */
>> folio = vma_alloc_folio(gfp_mask, 0, vma, addr, false);
>> if (!folio)
>> - return NULL;
>> + goto fail;
>> /*
>> * Swap entry may have been freed since our caller observed it.
>> @@ -466,7 +468,7 @@ struct page *__read_swap_cache_async(swp_entry_t entry, gfp_t gfp_mask,
>> folio_put(folio);
>> if (err != -EEXIST)
>> - return NULL;
>> + goto fail;
>> /*
>> * We might race against __delete_from_swap_cache(), and
>> @@ -500,12 +502,17 @@ struct page *__read_swap_cache_async(swp_entry_t entry, gfp_t gfp_mask,
>> /* Caller will initiate read into locked folio */
>> folio_add_lru(folio);
>> *new_page_allocated = true;
>> - return &folio->page;
>> + page = &folio->page;
>> +got_page:
>> + put_swap_device(si);
>> + return page;
>> fail_unlock:
>> put_swap_folio(folio, entry);
>> folio_unlock(folio);
>> folio_put(folio);
>> +fail:
>
> Maybe better "fail_put_swap".
>
> We now hold the swap device ref longer than we used to, prevent
> swapoff over the whole operation. I guess there is no way we can
> deadlock this way?
I think that we are safe. In swapoff() syscall, we call
percpu_ref_kill() after all pages are swapped in (via try_to_unuse()).
> In general, looks good to me.
Thanks!
Best Regards,
Huang, Ying
next prev parent reply other threads:[~2023-05-23 0:44 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-22 7:09 [PATCH -V2 0/5] swap: cleanup get/put_swap_device() usage Huang Ying
2023-05-22 7:09 ` [PATCH -V2 1/5] swap: Remove get/put_swap_device() in __swap_count() Huang Ying
2023-05-22 11:54 ` David Hildenbrand
2023-05-23 1:22 ` Yosry Ahmed
2023-05-23 1:47 ` Huang, Ying
2023-05-23 1:51 ` Yosry Ahmed
2023-05-22 7:09 ` [PATCH -V2 2/5] swap, __read_swap_cache_async(): enlarge get/put_swap_device protection range Huang Ying
2023-05-22 12:01 ` David Hildenbrand
2023-05-23 0:43 ` Huang, Ying [this message]
2023-05-22 7:09 ` [PATCH -V2 3/5] swap: remove __swp_swapcount() Huang Ying
2023-05-22 12:03 ` David Hildenbrand
2023-05-23 0:50 ` Huang, Ying
2023-05-22 7:09 ` [PATCH -V2 4/5] swap: remove get/put_swap_device() in __swap_duplicate() Huang Ying
2023-05-22 12:06 ` David Hildenbrand
2023-05-23 0:56 ` Huang, Ying
2023-05-23 7:59 ` David Hildenbrand
2023-05-23 1:39 ` Yosry Ahmed
2023-05-22 7:09 ` [PATCH -V2 5/5] swap: comments get_swap_device() with usage rule Huang Ying
2023-05-22 12:07 ` David Hildenbrand
2023-05-23 1:00 ` Huang, Ying
2023-05-23 1:37 ` Yosry Ahmed
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=87wn0zyj18.fsf@yhuang6-desk2.ccr.corp.intel.com \
--to=ying.huang@intel.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=minchan@kernel.org \
--cc=shy828301@gmail.com \
--cc=tim.c.chen@linux.intel.com \
--cc=willy@infradead.org \
--cc=yuzhao@google.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