linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Youngjun Park <youngjun.park@lge.com>
To: Andrew Morton <akpm@linux-foundation.org>
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>,
	youngjun.park@lge.com
Subject: [PATCH v2 0/5] mm: swap: small fixes and comment cleanups
Date: Fri, 31 Oct 2025 15:50:06 +0900	[thread overview]
Message-ID: <20251031065011.40863-1-youngjun.park@lge.com> (raw)

Hello,
This series provides a few small fixes and cleanups for the swap code.

The first patch fixes a memory leak in an error path that was recently
introduced. The subsequent patches include minor logic adjustments and
the removal of redundant comments.

This version addresses feedback from Kairui Song. Thank you for the
review.

---
v1->v2:
 - Reworked the error path in setup_clusters() to use a single exit
   label as suggested by Kairui.
 - Added a Fixes: tag to the first patch to identify the commit that
   introduced.
 - Added Kairui's Reviewed-by tag.

Link to v1:
https://lore.kernel.org/linux-mm/20251029085659.2005942-1-youngjun.park@lge.com/
---

Youngjun Park (5):
  mm, swap: Fix memory leak in setup_clusters() error path
  mm, swap: Use SWP_SOLIDSTATE to determine if swap is rotational
  mm, swap: Remove redundant comment for read_swap_cache_async
  mm: swap: change swap_alloc_slow() to void
  mm: swap: remove scan_swap_map_slots() references from comments

 mm/swap_state.c |  4 ----
 mm/swapfile.c   | 34 +++++++++++++++-------------------
 2 files changed, 15 insertions(+), 23 deletions(-)

base-commit: df412f2f12d492234da858e4dbaeabed9ecff3c4 (mm-new)
-- 
2.34.1



             reply	other threads:[~2025-10-31  6:54 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-31  6:50 Youngjun Park [this message]
2025-10-31  6:50 ` [PATCH v2 1/5] mm, swap: Fix memory leak in setup_clusters() error path Youngjun Park
2025-11-01  0:01   ` Baoquan He
2025-11-05  4:30   ` Chris Li
2025-10-31  6:50 ` [PATCH v2 2/5] mm, swap: Use SWP_SOLIDSTATE to determine if swap is rotational Youngjun Park
2025-11-01  0:02   ` Baoquan He
2025-11-05  4:30   ` Chris Li
2025-10-31  6:50 ` [PATCH v2 3/5] mm, swap: Remove redundant comment for read_swap_cache_async Youngjun Park
2025-11-01  0:02   ` Baoquan He
2025-11-05  6:03   ` Chris Li
2025-11-05  7:58     ` Chris Li
2025-11-05  9:27       ` YoungJun Park
2025-11-06  0:29       ` Andrew Morton
2025-11-20  5:00         ` Chris Li
2025-11-20 16:54           ` Andrew Morton
2025-11-20 18:34             ` Chris Li
2025-10-31  6:50 ` [PATCH v2 4/5] mm: swap: change swap_alloc_slow() to void Youngjun Park
2025-11-01  0:03   ` Baoquan He
2025-11-05  6:04   ` Chris Li
2025-10-31  6:50 ` [PATCH v2 5/5] mm: swap: remove scan_swap_map_slots() references from comments Youngjun Park
2025-11-01  0:03   ` Baoquan He
2025-11-05  6:50   ` Chris Li

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=20251031065011.40863-1-youngjun.park@lge.com \
    --to=youngjun.park@lge.com \
    --cc=akpm@linux-foundation.org \
    --cc=baohua@kernel.org \
    --cc=bhe@redhat.com \
    --cc=chrisl@kernel.org \
    --cc=kasong@tencent.com \
    --cc=linux-mm@kvack.org \
    --cc=nphamcs@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