linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Miaohe Lin <linmiaohe@huawei.com>
To: Hugh Dickins <hughd@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	<linux-kernel@vger.kernel.org>, <linux-mm@kvack.org>,
	Matthew Wilcox <willy@infradead.org>
Subject: Re: [PATCH next] mm/shmem: fix shmem folio swapoff hang
Date: Mon, 23 May 2022 09:50:34 +0800	[thread overview]
Message-ID: <2e4d5ba4-3525-322d-2aa6-3387d9822f5e@huawei.com> (raw)
In-Reply-To: <c32bee8a-f0aa-245-f94e-24dd271924fa@google.com>

On 2022/5/22 10:53, Hugh Dickins wrote:
> Shmem swapoff makes no progress: the index to indices is not incremented.

Yes, there would be a infinite loop in the while loop in shmem_unuse_inode().

> But "ret" is no longer a return value, so use folio_batch_count() instead.
> 
> Fixes: da08e9b79323 ("mm/shmem: convert shmem_swapin_page() to shmem_swapin_folio()")
> Signed-off-by: Hugh Dickins <hughd@google.com>

This patch looks good to me! Thanks!

Reviewed-by: Miaohe Lin <linmiaohe@huawei.com>
Tested-by: Miaohe Lin <linmiaohe@huawei.com>

BTW: When I try to fix infinite loop when swap in shmem error at swapoff time, I also found this
issue last Saturday [1]. ;)

[1] https://lore.kernel.org/linux-mm/0f6dc98b-88f4-c0c9-eb7b-5356ad0e08b1@huawei.com/

> ---
> 
>  mm/shmem.c |    3 +--
>  1 file changed, 1 insertion(+), 2 deletions(-)
> 
> --- a/mm/shmem.c
> +++ b/mm/shmem.c
> @@ -1171,7 +1171,6 @@ static int shmem_find_swap_entries(struc
>  	XA_STATE(xas, &mapping->i_pages, start);
>  	struct folio *folio;
>  	swp_entry_t entry;
> -	unsigned int ret = 0;
>  
>  	rcu_read_lock();
>  	xas_for_each(&xas, folio, ULONG_MAX) {
> @@ -1189,7 +1188,7 @@ static int shmem_find_swap_entries(struc
>  		if (swp_type(entry) != type)
>  			continue;
>  
> -		indices[ret] = xas.xa_index;
> +		indices[folio_batch_count(fbatch)] = xas.xa_index;
>  		if (!folio_batch_add(fbatch, folio))
>  			break;
>  
> 
> .
> 



      reply	other threads:[~2022-05-23  1:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-22  2:53 Hugh Dickins
2022-05-23  1:50 ` Miaohe Lin [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=2e4d5ba4-3525-322d-2aa6-3387d9822f5e@huawei.com \
    --to=linmiaohe@huawei.com \
    --cc=akpm@linux-foundation.org \
    --cc=hughd@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --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