From: Baolin Wang <baolin.wang@linux.alibaba.com>
To: Chris Down <chris@chrisdown.name>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Vineeth Pillai <vineeth@bitbyteword.org>,
Hugh Dickins <hughd@google.com>, Chris Li <chrisl@kernel.org>,
Kairui Song <kasong@tencent.com>, Nhat Pham <nphamcs@gmail.com>,
Baoquan He <baoquan.he@linux.dev>, Barry Song <baohua@kernel.org>,
Youngjun Park <youngjun.park@lge.com>,
Ying Huang <huang.ying.caritas@gmail.com>,
Kelley Nielsen <kelleynnn@gmail.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
kernel-team@meta.com, stable@vger.kernel.org
Subject: Re: [PATCH v2] mm: Make swapoff interruptible when unusing mms/shmem
Date: Tue, 27 Oct 2026 09:28:55 +0800 [thread overview]
Message-ID: <7346ff85-4941-45ea-951c-322c385704f0@linux.alibaba.com> (raw)
In-Reply-To: <at9kJwdGkHPsWwgG@chrisdown.name>
On 10/26/26 10:31 PM, Chris Down wrote:
> try_to_unuse() only checks for a pending signal between mms, and
> shmem_unuse() doesn't check at all. That means that once swapoff gets to
> a process or a shmem file with a lot swapped out, nothing can interrupt
> it until every last page of it has been read back in.
>
> Just as one example of where this can concretely show up, freezing tasks
> for suspend or hibernation has to wait for swapoff to notice the
> freezer's fake signal, and gives up after freeze_timeout_msecs (20
> seconds by default).
>
> Here's a facetious example where one swaps out 2GiB of one process to a
> swap file on ext4, starts swapoff, and half a second later tries to
> freeze with pm_test=freezer. Writing to /sys/power/state then fails with
> EBUSY and this in dmesg:
>
> Freezing user space processes failed after 20.003 seconds (1 tasks refusing to freeze, wq_busy=0):
> task:swapoff state:D stack:0 pid:3175 tgid:3175 ppid:2955 task_flags:0x400100 flags:0x00000419
> Call trace:
> [...]
> io_schedule+0x44/0x70
> folio_wait_bit_common+0x1ec/0x3d0
> __folio_lock+0x24/0x40
> unuse_pte_range+0x2d0/0x348
> unuse_vma+0x158/0x248
> unuse_mm+0xfc/0x150
> try_to_unuse+0x104/0x3f8
> __do_sys_swapoff+0x220/0x5d8
> [...]
>
> The same goes for anything else that wants swapoff to stop, like an
> admin hitting ^C in a panic, of course.
>
> Prior to commit b56a2d8af914 ("mm: rid swapoff of quadratic complexity")
> try_to_unuse() was driven by find_next_to_unuse() which checks for a
> signal before every entry, so let's restore that behaviour.
>
> Just as an example of the improvements, here's how long freezing takes
> in the same test while swapoff is happening on my computer:
>
> before after
> 400MiB anon 8.925s 0.028s
> 400MiB shmem 1.639s 0.003s
> 2GiB anon failed after 20.003s 0.011s
>
> Fixes: b56a2d8af914 ("mm: rid swapoff of quadratic complexity")
> Cc: stable@vger.kernel.org
> Acked-by: Vineeth Pillai (Google) <vineeth@bitbyteword.org>
> Signed-off-by: Chris Down <chris@chrisdown.name>
> ---
LGTM.
Reviewed-by: Baolin Wang <baolin.wang@linux.alibaba.com>
next prev parent reply other threads:[~2026-10-27 1:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 23:17 [PATCH] " Chris Down
2026-09-30 23:46 ` Andrew Morton
2026-10-01 12:50 ` Vineeth Remanan Pillai
2026-10-08 3:16 ` Baolin Wang
2026-10-26 14:04 ` Chris Down
2026-10-26 14:31 ` [PATCH v2] " Chris Down
2026-10-27 1:28 ` Baolin Wang [this message]
2026-10-27 11:50 ` Kairui Song
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=7346ff85-4941-45ea-951c-322c385704f0@linux.alibaba.com \
--to=baolin.wang@linux.alibaba.com \
--cc=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=baoquan.he@linux.dev \
--cc=chris@chrisdown.name \
--cc=chrisl@kernel.org \
--cc=huang.ying.caritas@gmail.com \
--cc=hughd@google.com \
--cc=kasong@tencent.com \
--cc=kelleynnn@gmail.com \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nphamcs@gmail.com \
--cc=rafael.j.wysocki@intel.com \
--cc=stable@vger.kernel.org \
--cc=vineeth@bitbyteword.org \
--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
all inboxes | Powered by JetHome®