From: Andrew Morton <akpm@linux-foundation.org>
To: Kairui Song <ryncsn@gmail.com>
Cc: linux-mm@kvack.org, Kemeng Shi <shikemeng@huaweicloud.com>,
Kairui Song <kasong@tencent.com>, Nhat Pham <nphamcs@gmail.com>,
Baoquan He <bhe@redhat.com>, Barry Song <baohua@kernel.org>,
Chris Li <chrisl@kernel.org>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
David Hildenbrand <david@redhat.com>,
"Matthew Wilcox (Oracle)" <willy@infradead.org>,
Ying Huang <ying.huang@linux.alibaba.com>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH 0/4] mm, swap: misc cleanup and bugfix
Date: Tue, 7 Oct 2025 15:20:36 -0700 [thread overview]
Message-ID: <20251007152036.cfbd572d706c40ed79d75642@linux-foundation.org> (raw)
In-Reply-To: <20251007-swap-clean-after-swap-table-p1-v1-0-74860ef8ba74@tencent.com>
On Tue, 07 Oct 2025 04:02:32 +0800 Kairui Song <ryncsn@gmail.com> wrote:
> A few cleanups and a bugfix that are either suitable after the swap
> table phase I or found during code review.
>
> Patch 1 is a bugfix and needs to be included in the stable branch,
> the rest have no behavior change.
fyi, the presentation of the series suggests that [1/4] is not a hotfix
- that it won't hit mainline (and then -stable) until after 6.19-rc1.
Which sounds OK given this:
> So far, no issues have been observed or reported with typical SSD setups
> under months of high pressure. This issue was found during my code
> review. But by hacking the kernel a bit: adding a mdelay(100) in the
> async discard path, this issue will be observable with WARNING triggered
> by the wrong GFP and cond_resched in the bio layer.
prev parent reply other threads:[~2025-10-07 22:20 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-06 20:02 [PATCH 0/4] mm, swap: misc cleanup and bugfix Kairui Song
2025-10-06 20:02 ` [PATCH 1/4] mm, swap: do not perform synchronous discard during allocation Kairui Song
2025-10-07 23:52 ` Nhat Pham
2025-10-08 20:54 ` Chris Li
2025-10-09 15:32 ` Kairui Song
2025-10-09 16:58 ` Chris Li
2025-10-12 16:49 ` Kairui Song
2025-10-14 21:27 ` Chris Li
2025-10-15 2:55 ` Chris Li
2025-10-15 6:24 ` Kairui Song
2025-10-15 16:45 ` Kairui Song
2025-10-21 6:48 ` Chris Li
2025-10-21 8:44 ` Kairui Song
2025-10-21 7:34 ` YoungJun Park
2025-10-24 4:00 ` Kairui Song
2025-10-06 20:02 ` [PATCH 2/4] mm, swap: rename helper for setup bad slots Kairui Song
2025-10-07 23:47 ` Nhat Pham
2025-10-08 10:25 ` David Hildenbrand
2025-10-08 20:58 ` Chris Li
2025-10-06 20:02 ` [PATCH 3/4] mm, swap: cleanup swap entry allocation parameter Kairui Song
2025-10-06 20:07 ` Kairui Song
2025-10-07 23:49 ` Nhat Pham
2025-10-08 10:26 ` David Hildenbrand
2025-10-08 20:59 ` Chris Li
2025-10-14 3:12 ` Baolin Wang
2025-10-06 20:02 ` [PATCH 4/4] mm/migrate, swap: drop usage of folio_index Kairui Song
2025-10-07 23:48 ` Nhat Pham
2025-10-08 1:20 ` Andrew Morton
2025-10-09 15:33 ` Kairui Song
2025-10-08 21:03 ` Chris Li
2025-10-14 3:15 ` Baolin Wang
2025-10-07 22:20 ` Andrew Morton [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=20251007152036.cfbd572d706c40ed79d75642@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=bhe@redhat.com \
--cc=chrisl@kernel.org \
--cc=david@redhat.com \
--cc=kasong@tencent.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nphamcs@gmail.com \
--cc=ryncsn@gmail.com \
--cc=shikemeng@huaweicloud.com \
--cc=stable@vger.kernel.org \
--cc=willy@infradead.org \
--cc=ying.huang@linux.alibaba.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