All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Matthew Wilcox (Oracle)" <willy@infradead.org>
Cc: yukuai@fygo.io, linux-raid@vger.kernel.org
Subject: Re: [PATCH 2/3] md: Use folio APIs in free_page()
Date: Mon, 14 Sep 2026 04:31:29 +0000	[thread overview]
Message-ID: <20260914043129.C6F8D1F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260914041830.2072626-2-willy@infradead.org>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:

Pre-existing issues:
- [High] Memory leak of internal bitmap pages and uninitialized file bitmap pages during teardown or error handling due to an early return in free_buffers().
--

commit d68f524234e61e6567e52a27e09b9d2546ab54af
Author: Matthew Wilcox (Oracle) <willy@infradead.org>

md: Use folio APIs in free_page()

This commit converts the page to a folio, removing some of the last uses of
a few page APIs and replacing two calls to compound_head() with one.

> diff --git a/drivers/md/md-bitmap.c b/drivers/md/md-bitmap.c
> index 5f1637f974c15..7b42db87d536d 100644
> --- a/drivers/md/md-bitmap.c
> +++ b/drivers/md/md-bitmap.c
> @@ -533,19 +533,18 @@ static void write_file_page(struct bitmap *bitmap, struct page *page, int wait)
>  
>  static void free_buffers(struct page *page)
>  {
> -	struct buffer_head *bh;
> +	struct folio *folio = page_folio(page);
> +	struct buffer_head *bh = folio_detach_private(folio);
>  
> -	if (!PagePrivate(page))
> +	if (!bh)
>  		return;

[Severity: High]
This is a pre-existing issue, but this early return skips the folio_put()
required to drop the base allocation reference for pages that do not have
buffers attached.

For internal bitmaps, pages are allocated via alloc_page() with a refcount
of 1 in md_bitmap_storage_alloc():

drivers/md/md-bitmap.c:md_bitmap_storage_alloc() {
	...
	store->filemap[pnum] = alloc_page(GFP_KERNEL|__GFP_ZERO);
	...
}

During MD array teardown or failure, md_bitmap_file_unmap() calls
free_buffers() on these pages:

drivers/md/md-bitmap.c:md_bitmap_file_unmap() {
	...
	free_buffers(map[pages]);
	...
}

Because internal bitmap pages don't have buffers attached, (!bh) evaluates
to true, triggering the early return and completely bypassing the folio_put()
at the end of the function.

This permanently leaks the pages allocated for the internal bitmap's filemap
and superblock.

Does this early return need to be updated so that folio_put() is still
called for folios without buffers?

> -	bh = page_buffers(page);
>  	while (bh) {
>  		struct buffer_head *next = bh->b_this_page;
>  		free_buffer_head(bh);
>  		bh = next;
>  	}
> -	detach_page_private(page);
> -	put_page(page);
> +	folio_put(folio);
>  }

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260913-remove-pg_private-v4-0-848550f7574e@nvidia.com?part=2

  reply	other threads:[~2026-09-14  4:31 UTC|newest]

Thread overview: 77+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-14  2:23 [PATCH v4 00/16] Remove PG_private by using page/folio->private checks instead Zi Yan
2026-09-14  2:23 ` Zi Yan
2026-09-14  2:23 ` [f2fs-dev] " Zi Yan via Linux-f2fs-devel
2026-09-14  2:23 ` [PATCH v4 01/16] mm/zsmalloc: replace PG_private with pointer comparison Zi Yan
2026-09-14  2:24 ` [PATCH v4 02/16] perf/ring_buffer: stop using PG_private as AUX page high-order marker Zi Yan
2026-09-14  2:36   ` sashiko-bot
2026-09-14  2:24 ` [PATCH v4 03/16] xen/grant-table: stop setting PG_private on pages for grant mapping Zi Yan
2026-09-14 13:15   ` David Hildenbrand (Arm)
2026-09-14  2:24 ` [PATCH v4 04/16] fscrypt: stop setting PG_private on bounce page Zi Yan
2026-09-14  2:24 ` [PATCH v4 05/16] mm/hugetlb: use direct assignment instead of folio_change_private() Zi Yan
2026-09-14  2:58   ` Muchun Song
2026-09-14 13:16   ` David Hildenbrand (Arm)
2026-09-16  1:56   ` Zi Yan
2026-09-16  6:12     ` David Hildenbrand (Arm)
2026-09-18  1:41       ` Zi Yan
2026-09-18  3:13         ` Muchun Song
2026-09-14  2:24 ` [f2fs-dev] [PATCH v4 06/16] f2fs: stop using PG_private Zi Yan via Linux-f2fs-devel
2026-09-14  2:24   ` Zi Yan
2026-09-14 13:17   ` [f2fs-dev] " David Hildenbrand (Arm) via Linux-f2fs-devel
2026-09-14 13:17     ` David Hildenbrand (Arm)
2026-09-14  2:24 ` [f2fs-dev] [PATCH v4 07/16] f2fs: convert the ->private flag helpers to folio-only Zi Yan via Linux-f2fs-devel
2026-09-14  2:24   ` Zi Yan
2026-09-16  2:20   ` [f2fs-dev] " Zi Yan via Linux-f2fs-devel
2026-09-16  2:20     ` Zi Yan
2026-09-14  2:24 ` [PATCH v4 08/16] erofs: mm/pagemap: add readahead_folio_last() to avoid folio->private Zi Yan
2026-09-14  2:24 ` [PATCH v4 09/16] erofs: use folio_attach/detach_private() instead of direct assignment Zi Yan
2026-09-14 13:18   ` David Hildenbrand (Arm)
2026-09-14  2:24 ` [PATCH v4 10/16] mm/page-flags: check page/folio->private instead of PG_private Zi Yan
2026-09-14 13:26   ` David Hildenbrand (Arm)
2026-09-14 14:44     ` Zi Yan
2026-09-14 15:11       ` David Hildenbrand (Arm)
2026-09-14 15:21         ` Zi Yan
2026-09-14  2:24 ` [PATCH v4 11/16] treewide: remove folio_set/clear_private() usage Zi Yan
2026-09-14  2:24 ` [PATCH v4 12/16] ceph: replace PagePrivate() with page_private() Zi Yan
2026-09-14 13:26   ` David Hildenbrand (Arm)
2026-09-14  2:24 ` [PATCH v4 13/16] md/md-bitmap: " Zi Yan
2026-09-14  2:24 ` [PATCH v4 14/16] buffer: replace page_buffer() with page_private() and delete it Zi Yan
2026-09-14  2:24 ` [PATCH v4 15/16] treewide: remove PagePrivate() and PG_private from comments and docs Zi Yan
2026-09-14  2:24   ` Zi Yan
2026-09-14 13:36   ` David Hildenbrand (Arm)
2026-09-14 13:36     ` David Hildenbrand (Arm)
2026-09-14  2:24 ` [PATCH v4 16/16] mm/page-flags: remove PG_private Zi Yan
2026-09-14  2:47   ` sashiko-bot
2026-09-14 13:37     ` David Hildenbrand (Arm)
2026-09-14 13:38   ` David Hildenbrand (Arm)
2026-09-14  3:39 ` [PATCH v4 00/16] Remove PG_private by using page/folio->private checks instead Andrew Morton
2026-09-14  3:39   ` Andrew Morton
2026-09-14  3:39   ` [f2fs-dev] " Andrew Morton
2026-09-15 17:16   ` Zi Yan
2026-09-15 17:16     ` Zi Yan
2026-09-15 17:16     ` [f2fs-dev] " Zi Yan via Linux-f2fs-devel
2026-09-15 18:18   ` Zi Yan via Linux-f2fs-devel
2026-09-14  4:18 ` [PATCH 1/3] md: Use folio_alloc_buffers() Matthew Wilcox (Oracle)
2026-09-14  4:27   ` sashiko-bot
2026-09-14 13:12   ` David Hildenbrand (Arm)
2026-09-14 13:17     ` Matthew Wilcox
2026-09-14 13:20       ` David Hildenbrand (Arm)
2026-09-14 14:36         ` Zi Yan
2026-09-14  4:18 ` [PATCH 2/3] md: Use folio APIs in free_page() Matthew Wilcox (Oracle)
2026-09-14  4:31   ` sashiko-bot [this message]
2026-09-14 16:21     ` Matthew Wilcox
2026-09-14 16:25       ` Zi Yan
2026-09-14 13:13   ` David Hildenbrand (Arm)
2026-09-14  4:18 ` [PATCH 3/3] md: Remove the last use of page_buffers() Matthew Wilcox (Oracle)
2026-09-14  4:29   ` sashiko-bot
2026-09-14 13:14   ` David Hildenbrand (Arm)
2026-09-14  4:21 ` [PATCH v4 00/16] Remove PG_private by using page/folio->private checks instead Matthew Wilcox
2026-09-14  4:21   ` Matthew Wilcox
2026-09-14  4:21   ` [f2fs-dev] " Matthew Wilcox
2026-09-14 13:10   ` David Hildenbrand (Arm)
2026-09-14 13:10     ` David Hildenbrand (Arm)
2026-09-14 13:10     ` [f2fs-dev] " David Hildenbrand (Arm) via Linux-f2fs-devel
2026-09-14 15:30 ` patchwork-bot+f2fs
2026-09-14 15:30   ` patchwork-bot+f2fs
2026-09-14 15:30   ` patchwork-bot+f2fs--- via Linux-f2fs-devel
2026-09-15 21:49 ` Andrew Morton
2026-09-15 23:14   ` Roman Gushchin

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=20260914043129.C6F8D1F000FF@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=willy@infradead.org \
    --cc=yukuai@fygo.io \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.