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=1794273831; b=nvnH8W/zavXfTbIRCTBqy++Ykw7qw1hp5mZ8ay8HLRY21iQgajvmHpp2GZq1wK52FbxO p6uJPx8KEWLi8gjyz+efs3gBoCoaemTaHoy0I0zPvmsmplALbttNQseES9Vq4i7NDpojz Zq6fSuH8jI4qJ+edjfI0oE/B2TJZMxtNVAqzW0R7e9QECxTRiyVwYYdDi94vtTzzLua0f KhqQYbN/Qqtn1LOjVN85Pt0WwqfH5szTcZOgx+/98J1/Mw8GdG0R5F00q3FitWCBN5mqs HeH1PA9gIDYwO5T2SS8B1GUzr+AMMvZBsGgVcPpcsOgjd4R+4e6FNhSQD+IIGayklRA== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1794273831; h=Received:DKIM-Signature:From:To:Cc:Subject:Date:Message-ID:X-Mailer: MIME-Version:Content-Type:Content-Transfer-Encoding; bh=ZaZyGtL7FjD0BsecUntZialrNmqUthcFRttx55ZWEn8=; b=jG+F6wlMJzqXbaKrd7hh1XVuUl5Ee4DM+zx8AWIlO/K8I8/3otCQFAyqwQcsvB9+pes2 h0UhKIMbxw5Pu4CkQNHcIJ0iNUkmZ//lJRI6CoQmik+ZXlr9hqCUlzN7rNhdF/V8X8ug6 5M2LOXLRQN85CbgCP1L4ptZT4LftVVPTcEqHh+Uk1vFLuYEX8HNFXdShaRWk6hUsQHgbS oJ1+FzcEmVuojPq0XggPyFW84unTVYo+4XKMqisLxOwoEhF2ReONt4qcRA7ULSMD63B4e bOJPQQQwRgNMd6VM/GchtW6b0u+02sxVsRd5Mpndpij+AzBjNh4dUEcDpZkVOjH8+kw== ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dkim=pass header.d=kernel.org header.i=@kernel.org header.a=rsa-sha256 header.s=k20260515 header.b=RGRoTgfI; 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 2E91E60A260F for ; Tue, 10 Nov 2026 01:23:51 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.a=rsa-sha256 header.s=k20260515 header.b=RGRoTgfI Received: by smtp.kernel.org (Postfix) with ESMTPSA id 379651F0089F; Tue, 10 Nov 2026 01:23:50 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1794273831; bh=ZaZyGtL7FjD0BsecUntZialrNmqUthcFRttx55ZWEn8=; h=From:To:Cc:Subject:Date; b=RGRoTgfIV3fQvvY1pacuOTx0kjQbaXERZWbxuu0kZWBLbvD0Xnh4uF7A9WOhUNL77 up0xtCjyQDqVJXgsHMp00znIn6jyk/IrdzHK26+iD1M5pr93gCUrmZeXzKdwlCXvHu nR9/Gx+pnp+/6X8nvo/+CTFX6CYCcyqPTlmy6gp4ZlmWq5SF5KTWZTMW7yBf/Mqov3 zXZ4c4jm0k3E1XhRrKvyRBW8/RWKe6gMqaeQ38vQiDsbHArDmGr/iWb6w4nBK/xq1q 79NmcVxJB2M/p4s6at7FGJ8jViGThRBoyXaCB3i9a9k0tLOBR+gjFineFMHedjhBse dQApebe5Jym6Q== From: Sasha Levin To: david@kernel.org, josef@toxicpanda.com, ljs@kernel.org, pfalcato@suse.de, harry@kernel.org, usama.anjum@arm.com Cc: stable@vger.kernel.org Subject: FAILED: patch "[PATCH] mm/vma: don't leak the charge for stack growth" failed to apply to 5.15-stable tree Date: Mon, 9 Nov 2026 20:23:49 -0500 Message-ID: <20261109202349-failed-5.15-b1ee87802111@kernel.org> X-Mailer: git-send-email 2.53.0 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-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The patch below does not apply to the 5.15-stable tree. If someone wants it applied there, or to any other stable or longterm tree, then please email the backport, including the original git commit id to . To reproduce the conflict and resubmit, you may use the following commands: git fetch https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/ linux-5.15.y git checkout FETCH_HEAD git cherry-pick -x b1ee87802111156e27557e82acc31fa7dfc76e2a # git commit -s git send-email --to '' --in-reply-to '20261109202349-failed-5.15-b1ee87802111@kernel.org' --subject-prefix 'PATCH 5.15.y' 'HEAD^..' Thanks, Sasha ------------------ original commit in Linus's tree ------------------ >From b1ee87802111156e27557e82acc31fa7dfc76e2a Mon Sep 17 00:00:00 2001 From: "David Hildenbrand (Arm)" Date: Sat, 31 Oct 2026 10:40:13 +0100 Subject: [PATCH] mm/vma: don't leak the charge for stack growth acct_stack_growth() charges stack expansion even without VM_ACCOUNT. This can happen for read-only or MAP_NORESERVE mappings created with MAP_GROWSDOWN. Unmapping these VMAs does not release the charge, leaking Committed_AS. Only check and charge growth for VM_ACCOUNT VMAs, matching mremap(). Unaccounted growth skips the overcommit check while remaining subject to the other stack-growth limits. Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2") Cc: stable@vger.kernel.org Reported-by: Josef Bacik Reviewed-by: Lorenzo Stoakes (ARM) Reviewed-by: Pedro Falcato Reviewed-by: Harry Yoo (Meta) Tested-by: Muhammad Usama Anjum Link: https://patch.msgid.link/20261031-fixes_core-v3-44-d6437171ecc3@kernel.org Signed-off-by: David Hildenbrand (Arm) --- mm/vma.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/mm/vma.c b/mm/vma.c index acdf00346cda5..695d0be85ac86 100644 --- a/mm/vma.c +++ b/mm/vma.c @@ -3391,7 +3391,8 @@ static int acct_stack_growth(struct vm_area_struct *vma, * Overcommit.. This must be the final test, as it will * update security statistics. */ - if (security_vm_enough_memory_mm(mm, grow)) + if (vma_test(vma, VMA_ACCOUNT_BIT) && + security_vm_enough_memory_mm(mm, grow)) return -ENOMEM; return 0; -- 2.53.0