From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.remote-ip=100.103.45.18 ARC-Seal: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; cv=none; t=1794064518; b=q3qWWIvpCs1pGZvpaCq3QnXSJdu9SJqO6tnvgX3kyLuC4cQZAkU+PrloebUzkfgbE9eT kzt8c+Drr6cU+j7yMKFg/NrM6Eei3eevMvMChatFsDbTNeO8W+nWzeHAH4Dl2klsMtDY3 vV73WhMVgVeUZopw8uUzYw8FW1MaNBvco9wut+tkN0P87r9Cm+uRMz9ZLX5Rj5cBBKCez y2xMFXPHS5m33iuxV0QqIguCk3Px5hyiYCDyQ3nHSVSO4WBCymQPczBvJMCphbI8DPFtw hwUV9NgGwUj5lw+IdiCQisoFzaES8p+XHQT0vqM0n8/dQJ/XywNA5/GXGvPr3IYQgXw== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1794064518; h=Received:DKIM-Signature:From:To:Cc:Subject:Date:Message-ID:X-Mailer: In-Reply-To:References:User-Agent:X-stable:X-Patchwork-Hint: MIME-Version:Content-Transfer-Encoding; bh=5korLv9CQt31vE1ylwXmSIgPvAwwygkYgZpdn5rgXq4=; b=Sm6oYpWhKc6qslV7k65iVZIvyCGIBvFR1hIiZxxHjB8gBrwzkcoNN4cnZMmMlpDajqgB ogRvtEY8BUfmZuXa4WjGIf+2ccXMmxHOlLUJuVFUh/uNkpQ3E7uC3vQ68psS7oZ4G47Mj Kgy54byM36ImuwKK/crIBX2LIBAMOME4kBKeLvxH18Qc8VNc9/PGIuNFA20nfr+YnoW0m yPtJu68Ri0jFiBnQLGi7JEaDsXYZwLZ0eqXh4rWtQsX15dl8XEUKR/HrDcOgAavpwknG6 zLpFFccxCXaPa+AYslmZwtzNET9ZVS7zrV/fQ27fE5Mf5gUq+txH+XboAB/YhS/AuTQ== ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dkim=pass header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=korg header.b=AeqSk0yw; arc=none smtp.remote-ip=100.103.45.18 Received: from smtp.kernel.org (quasi.space.kernel.org [100.103.45.18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 694A2606B892; Sat, 7 Nov 2026 15:15:18 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=korg header.b=AeqSk0yw Received: by smtp.kernel.org (Postfix) with ESMTPSA id 1CD691F0089F; Sat, 7 Nov 2026 15:15:18 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1794064518; bh=5korLv9CQt31vE1ylwXmSIgPvAwwygkYgZpdn5rgXq4=; h=From:To:Cc:Subject:Date:In-Reply-To:References; b=AeqSk0ywyGzot0DWQNj+Bbe+V/JiRAuTcB56mabPBqjjKNQKVurWNZMDGgP4s9mHZ ypjyv4LQW/bvX4Q+uShGUaDy/5pcIlxJfiHzJFwHT+KOKtXrzD+s2eYemgNMTgUuyR TjOtPbYwU9Hwf7zMlTRYGvJm2Frvm6BVo3UmU2LI= From: Greg Kroah-Hartman To: stable@vger.kernel.org Cc: Greg Kroah-Hartman , patches@lists.linux.dev, Joe Damato , Andrew Morton , Shakeel Butt , Johannes Weiner , Michal Hocko , Muchun Song , Roman Gushchin , Sasha Levin Subject: [PATCH 7.3 0501/1257] mm: memcontrol: raise MEMCG_MAX for charges that fail without reclaiming Date: Sat, 7 Nov 2026 08:46:37 -0500 Message-ID: <20261107134953.267152896@linuxfoundation.org> X-Mailer: git-send-email 2.56.0 In-Reply-To: <20261107134939.434104957@linuxfoundation.org> References: <20261107134939.434104957@linuxfoundation.org> User-Agent: quilt/0.69 X-stable: review X-Patchwork-Hint: ignore X-Mailing-List: stable@vger.kernel.org List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list MIME-Version: 1.0 Content-Transfer-Encoding: 8bit 7.3-stable review patch. If anyone has any objections, please let me know. ------------------ From: Joe Damato [ Upstream commit 374f65b1481992eb6b9c6bffd53f3afa5c2e94cf ] Charges that exceed memory.max and return through the nomem label can raise no event and simply return -ENOMEM. A non-blocking charge can hit the limit, get rejected, but is not visible in memory.events. This was noticed in a production setting where bpf_mem_alloc() attempted to refill its per-cpu freelists, which triggered a non-blocking charge while at the limit. Commit d6e103a757fa ("mm: memcontrol: do not miss MEMCG_MAX events for enforced allocations") added raised_max_event to cover charges that are force charged without ever reaching reclaim, but charges that are rejected outright were left out. Getting an allocation failure without the corresponding MEMCG_MAX event is unexpected and makes debugging and monitoring harder. Raise the event on the way out for rejected charges as well, by routing the -ENOMEM return through the same exit path that already covers forced charges. The existing behavior of raising a MEMCG_MAX event on every charge/reclaim/retry iteration is left unchanged. Tested with a module that performs accounted GFP_NOWAIT page allocations from a task in a cgroup at its memory.max, and measures the resulting memory.events:max delta. Without this patch the rejected charges raise no event at all; with it the delta matches the number of rejected charges exactly. A GFP_KERNEL|__GFP_NORETRY control, which reaches reclaim, raises the same two events per failed charge before and after, confirming the existing charge/reclaim/retry accounting is unchanged. Link: https://lore.kernel.org/20260831174836.3102406-1-joe@dama.to Fixes: d6e103a757fa ("mm: memcontrol: do not miss MEMCG_MAX events for enforced allocations") Signed-off-by: Joe Damato Signed-off-by: Andrew Morton Suggested-by: Shakeel Butt Acked-by: Shakeel Butt Cc: Johannes Weiner Cc: Michal Hocko Cc: Muchun Song Cc: Roman Gushchin Cc: Signed-off-by: Sasha Levin --- mm/memcontrol.c | 28 ++++++++++++++++------------ 1 file changed, 16 insertions(+), 12 deletions(-) diff --git a/mm/memcontrol.c b/mm/memcontrol.c index 814eb56feb6f5..259f9f43b38b1 100644 --- a/mm/memcontrol.c +++ b/mm/memcontrol.c @@ -2661,10 +2661,11 @@ static int try_charge_memcg(struct mem_cgroup *memcg, gfp_t gfp_mask, bool raised_max_event = false; unsigned long pflags; bool allow_spinning = gfpflags_allow_spinning(gfp_mask); + int ret = 0; retry: if (consume_stock(memcg, nr_pages)) - return 0; + return ret; if (!allow_spinning) /* Avoid the refill and flush of the older stock */ @@ -2775,16 +2776,11 @@ static int try_charge_memcg(struct mem_cgroup *memcg, gfp_t gfp_mask, * put the burden of reclaim on regular allocation requests * and let these go through as privileged allocations. */ - if (!(gfp_mask & (__GFP_NOFAIL | __GFP_HIGH))) - return -ENOMEM; + if (!(gfp_mask & (__GFP_NOFAIL | __GFP_HIGH))) { + ret = -ENOMEM; + goto out; + } force: - /* - * If the allocation has to be enforced, don't forget to raise - * a MEMCG_MAX event. - */ - if (!raised_max_event) - __memcg_memory_event(mem_over_limit, MEMCG_MAX, allow_spinning); - /* * The allocation either can't fail or will lead to more memory * being freed very soon. Allow memory usage go over the limit @@ -2794,7 +2790,15 @@ static int try_charge_memcg(struct mem_cgroup *memcg, gfp_t gfp_mask, if (do_memsw_account()) page_counter_charge(&memcg->memsw, nr_pages); - return 0; +out: + /* + * Don't forget to raise a MEMCG_MAX event for forced or rejected + * requests. + */ + if (!raised_max_event) + __memcg_memory_event(mem_over_limit, MEMCG_MAX, allow_spinning); + + return ret; done_restock: if (batch > nr_pages) @@ -2853,7 +2857,7 @@ static int try_charge_memcg(struct mem_cgroup *memcg, gfp_t gfp_mask, !(current->flags & PF_MEMALLOC) && gfpflags_allow_blocking(gfp_mask)) __mem_cgroup_handle_over_high(gfp_mask); - return 0; + return ret; } static inline int try_charge(struct mem_cgroup *memcg, gfp_t gfp_mask, -- 2.53.0