From: Muchun Song <muchun.song@linux.dev>
To: Deepanshu Kartikey <kartikey406@gmail.com>
Cc: osalvador@suse.de, david@kernel.org, akpm@linux-foundation.org,
mike.kravetz@oracle.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org,
syzbot+226c1f947186f8fef796@syzkaller.appspotmail.com
Subject: Re: [PATCH] mm/hugetlb: fix hugetlb cgroup rsvd charge/uncharge mismatch
Date: Sun, 26 Apr 2026 11:47:26 +0800 [thread overview]
Message-ID: <9CC5F017-AE6A-4EB0-9099-B4DA5E93EA85@linux.dev> (raw)
In-Reply-To: <20260328065534.346053-1-kartikey406@gmail.com>
> On Mar 28, 2026, at 14:55, Deepanshu Kartikey <kartikey406@gmail.com> wrote:
>
> In alloc_hugetlb_folio(), a single h_cg pointer is used for both
> the rsvd and non-rsvd hugetlb cgroup charges. When map_chg is set,
> hugetlb_cgroup_charge_cgroup_rsvd() stores the charged cgroup in
> h_cg, but the immediately following hugetlb_cgroup_charge_cgroup()
> overwrites h_cg with the non-rsvd cgroup pointer.
>
> As a result, hugetlb_cgroup_commit_charge_rsvd() stores the wrong
> (non-rsvd) cgroup pointer into the folio's rsvd slot.
>
> When the folio is later freed, free_huge_folio() unconditionally
> calls both hugetlb_cgroup_uncharge_folio() and
> hugetlb_cgroup_uncharge_folio_rsvd(). The rsvd uncharge reads back
> the wrong cgroup from the folio and decrements a counter that was
> never charged for that cgroup, causing a page_counter underflow:
>
> page_counter underflow: -512 nr_pages=512
> WARNING: mm/page_counter.c:61 at page_counter_cancel
>
> Fix this by introducing a separate h_cg_rsvd pointer exclusively
> for the rsvd charge path, keeping the rsvd and non-rsvd charges
> fully independent through their charge, commit, and error uncharge
> paths.
>
> Fixes: 08cf9faf7558 ("hugetlb_cgroup: support noreserve mappings")
> Reported-by: syzbot+226c1f947186f8fef796@syzkaller.appspotmail.com
> Closes: https://syzkaller.appspot.com/bug?extid=226c1f947186f8fef796
> Signed-off-by: Deepanshu Kartikey <kartikey406@gmail.com>
Reviewed-by: Muchun Song <muchun.song@linux.dev>
Thanks.
prev parent reply other threads:[~2026-04-26 3:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-28 6:55 [PATCH] mm/hugetlb: fix hugetlb cgroup rsvd charge/uncharge mismatch Deepanshu Kartikey
2026-03-30 20:15 ` Andrew Morton
2026-04-25 14:57 ` Andrew Morton
2026-04-26 3:47 ` Muchun Song [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=9CC5F017-AE6A-4EB0-9099-B4DA5E93EA85@linux.dev \
--to=muchun.song@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=kartikey406@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@oracle.com \
--cc=osalvador@suse.de \
--cc=syzbot+226c1f947186f8fef796@syzkaller.appspotmail.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