linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Baoquan He <bhe@redhat.com>
To: Youngjun Park <youngjun.park@lge.com>
Cc: akpm@linux-foundation.org, chrisl@kernel.org, kasong@tencent.com,
	shikemeng@huaweicloud.com, nphamcs@gmail.com, baohua@kernel.org,
	linux-mm@kvack.org
Subject: Re: [PATCH] mm/swap: fix wrong plist empty check in swap_alloc_slow()
Date: Thu, 20 Nov 2025 10:47:20 +0800	[thread overview]
Message-ID: <aR6BOK+DbGyMNrTd@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20251119114136.594108-1-youngjun.park@lge.com>

On 11/19/25 at 08:41pm, Youngjun Park wrote:
> swap_alloc_slow() was checking `si->avail_list` instead of `next->avail_list`
> when verifying if the next swap device is still in the list, which could cause
> unnecessary restarts during allocation.
> 
> Fixes: 8e689f8ea45ff ("mm/swap: do not choose swap device according to numa node")
> Signed-off-by: Youngjun Park <youngjun.park@lge.com>
> ---
>  mm/swapfile.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

Thanks for the fix.

Reviewed-by: Baoquan He <bhe@redhat.com>

> 
> diff --git a/mm/swapfile.c b/mm/swapfile.c
> index 94e0f0c54168..cf780fefaf7d 100644
> --- a/mm/swapfile.c
> +++ b/mm/swapfile.c
> @@ -1374,7 +1374,7 @@ static bool swap_alloc_slow(swp_entry_t *entry,
>  		 * still in the swap_avail_head list then try it, otherwise
>  		 * start over if we have not gotten any slots.
>  		 */
> -		if (plist_node_empty(&si->avail_list))
> +		if (plist_node_empty(&next->avail_list))
>  			goto start_over;
>  	}
>  	spin_unlock(&swap_avail_lock);
> -- 
> 2.34.1
> 



      parent reply	other threads:[~2025-11-20  2:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-19 11:41 Youngjun Park
2025-11-19 13:02 ` Kairui Song
2025-11-19 16:37   ` YoungJun Park
2025-11-20  2:08     ` Kairui Song
2025-11-20  2:06   ` YoungJun Park
2025-11-20  2:18     ` Kairui Song
2025-11-21  6:54       ` YoungJun Park
2025-11-21 16:56         ` Kairui Song
2025-11-20  2:47 ` Baoquan He [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=aR6BOK+DbGyMNrTd@MiWiFi-R3L-srv \
    --to=bhe@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=baohua@kernel.org \
    --cc=chrisl@kernel.org \
    --cc=kasong@tencent.com \
    --cc=linux-mm@kvack.org \
    --cc=nphamcs@gmail.com \
    --cc=shikemeng@huaweicloud.com \
    --cc=youngjun.park@lge.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