From: YoungJun Park <youngjun.park@lge.com>
To: Kairui Song <ryncsn@gmail.com>
Cc: akpm@linux-foundation.org, chrisl@kernel.org,
shikemeng@huaweicloud.com, nphamcs@gmail.com, bhe@redhat.com,
baohua@kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH 1/2] mm/swapfile: fix list iteration in swap_sync_discard
Date: Thu, 27 Nov 2025 11:22:23 +0900 [thread overview]
Message-ID: <aSe131xi3VChbWzw@yjaykim-PowerEdge-T330> (raw)
In-Reply-To: <CAMgjq7C0BVx8OVhEgJu3sVTAgTMrh_-vs9OrmwQhyFX6xC_LKw@mail.gmail.com>
On Thu, Nov 27, 2025 at 02:23:05AM +0800, Kairui Song wrote:
> On Wed, Nov 26, 2025 at 12:31 AM Youngjun Park <youngjun.park@lge.com> wrote:
> >
> > swap_sync_discard() has an issue where if the next device becomes full
> > and is removed from the plist during iteration, the operation fails
> > even when other swap devices with pending discard entries remain
> > available.
> >
> > Fix by checking plist_node_empty(&next->list) and restarting iteration
> > when the next node is removed during discard operations.
> >
> > Additionally, switch from swap_avail_lock/swap_avail_head to swap_lock/
> > swap_active_head. This means the iteration is only affected by swapoff
> > operations rather than frequent availability changes, reducing
> > exceptional condition checks and lock contention.
> >
> > Fixes: 686ea517f471 ("mm, swap: do not perform synchronous discard during allocation")
> > Suggested-by: Kairui Song <kasong@tencent.com>
> > Signed-off-by: Youngjun Park <youngjun.park@lge.com>
> > ---
> > mm/swapfile.c | 18 +++++++++++-------
> > 1 file changed, 11 insertions(+), 7 deletions(-)
> >
> > diff --git a/mm/swapfile.c b/mm/swapfile.c
> > index d12332423a06..998271aa09c3 100644
> > --- a/mm/swapfile.c
> > +++ b/mm/swapfile.c
> > @@ -1387,21 +1387,25 @@ static bool swap_sync_discard(void)
> > bool ret = false;
> > struct swap_info_struct *si, *next;
> >
> > - spin_lock(&swap_avail_lock);
> > - plist_for_each_entry_safe(si, next, &swap_avail_head, avail_list) {
> > - spin_unlock(&swap_avail_lock);
> > + spin_lock(&swap_lock);
> > +start_over:
> > + plist_for_each_entry_safe(si, next, &swap_active_head, list) {
> > + spin_unlock(&swap_lock);
> > if (get_swap_device_info(si)) {
> > if (si->flags & SWP_PAGE_DISCARD)
> > ret = swap_do_scheduled_discard(si);
> > put_swap_device(si);
> > }
> > if (ret)
> > - return true;
> > - spin_lock(&swap_avail_lock);
> > + return ret;
>
> Nit: I'd prefer to avoid unnecessary changes like this, `return true`
> is the same thing. No need to send an update for this though, a really
> trivial issue.
Okay, I will revert it to the original code.
> > +
> > + spin_lock(&swap_lock);
> > + if (plist_node_empty(&next->list))
> > + goto start_over;
> > }
> > - spin_unlock(&swap_avail_lock);
> > + spin_unlock(&swap_lock);
> >
> > - return false;
> > + return ret;
> > }
> >
> > /**
> > --
> > 2.34.1
>
> Thanks!
>
> Acked-by: Kairui Song <kasong@tencent.com>
>
Thank you
Youngjun Park
next prev parent reply other threads:[~2025-11-27 2:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-25 16:30 [PATCH 0/2] mm/swapfile: fix and cleanup swap list iterations Youngjun Park
2025-11-25 16:30 ` [PATCH 1/2] mm/swapfile: fix list iteration in swap_sync_discard Youngjun Park
2025-11-26 18:23 ` Kairui Song
2025-11-27 2:22 ` YoungJun Park [this message]
2025-11-27 2:15 ` Baoquan He
2025-11-27 2:54 ` YoungJun Park
2025-11-27 5:42 ` YoungJun Park
2025-11-27 8:06 ` Baoquan He
2025-11-27 9:34 ` YoungJun Park
2025-11-27 10:32 ` Baoquan He
2025-11-27 10:44 ` YoungJun Park
2025-11-27 10:50 ` Baoquan He
2025-11-25 16:30 ` [PATCH 2/2] mm/swapfile: use plist_for_each_entry in __folio_throttle_swaprate Youngjun Park
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=aSe131xi3VChbWzw@yjaykim-PowerEdge-T330 \
--to=youngjun.park@lge.com \
--cc=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=bhe@redhat.com \
--cc=chrisl@kernel.org \
--cc=linux-mm@kvack.org \
--cc=nphamcs@gmail.com \
--cc=ryncsn@gmail.com \
--cc=shikemeng@huaweicloud.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