Re: [PATCH v2 0/5] mm, swap: misc cleanup and bugfix

[Kairui Song <ryncsn@gmail.com>]

On Fri, Oct 24, 2025 at 9:18 PM Lorenzo Stoakes
<lorenzo.stoakes@oracle.com> wrote:
>
> On Fri, Oct 24, 2025 at 02:00:38AM +0800, Kairui Song 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.
> >
> > ---
> > Changes in v2:
> > - Update commit message for patch 1, it's a sub-optimal fix and a better
> >   fix can be done later. [ Chris Li ]
> > - Fix a lock balance issue in patch 1. [ YoungJun Park ]
> > - Add a trivial cleanup patch to remove an unused argument,
> >   no behavior change.
> > - Update kernel doc.
> > - Fix minor issue with commit message [ Nhat Pham ]
> > - Link to v1: https://lore.kernel.org/r/20251007-swap-clean-after-swap-table-p1-v1-0-74860ef8ba74@tencent.com
> >
> > ---
> > Kairui Song (5):
> >       mm, swap: do not perform synchronous discard during allocation
>
> FYI For some reason this commit is not present on lore, see [0]
>
> [0]: https://lore.kernel.org/all/20251024-swap-clean-after-swap-table-p1-v2-0-a709469052e7@tencent.com/

Thanks for letting me know, strangely, it is here:
https://lkml.kernel.org/r/20251024-swap-clean-after-swap-table-p1-v2-1-c5b0e1092927@tencent.com

But the In-reply-to id is wrong. I'm using b4 and somehow patch 1 was
blocked by gmail's SMTP so I had to try to resend patch 1 again,
something went wrong with that part. I'll try to find out the problem
and avoid that from happening again.

I'm seeing that patch 1 is being merged into mm tree just fine, I
guess that should be OK.

If anyone is reading the threads, this url above should be helpful.