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=1794273247; b=kSnMMl2p9zYuhEv3riU5rmiKE/xWzs2/GAsRTAdWPb5b9/jia9oLviCkSJq5ElFushPk rkubeZX8l9O6LSU5jdiTffUynj0c19u6tqupAdcbYVFsnzj/clQujyHfJe9KmJnPTn3sx AUJpOXRf+uawYmrb839SDEGd7f10d2Kt/AlEoCEuF5dyRhV9qH9P1UtWU0hNFUppVKJ0f hY3kbpHK2ojMfwTAFHbAgin7x6Jg8FO+zv3K5TF7eMU1WmSNBsX8fcCFP46Fh1yqBqLkS r7AguXA9ky7Q/dl987wAwtidx2r8VcIv/w6EzKQbejH/ehLgw/pcBJUinjt9ZYaHRYg== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1794273247; h=Received:DKIM-Signature:From:To:Cc:Subject:Date:Message-ID:X-Mailer: MIME-Version:Content-Type:Content-Transfer-Encoding; bh=0erLcdDfB3B910fHzg9R2k7tdGf2oO8vvq/0TsBK3JM=; b=zvIwC4TAJFFLunipryf9Y4mftU6vuDYJ9kICiyNzsH49eVFhjDUrVdwtm7O55jxg0MES zbumJ1HQ3CEtY9aZrbsYm4QUmoIl1tCgAobZf8XmkgcPsjo2HYBaS7IVHXPARsTnW2P/I h/FLAZ55lT1qeXdX0N07gxLRK9cB21sJjcuignXOFufbQm1v8UZmlltytsxxshZ1qKCIl 4BlhMaKa3ETwVcclayujbZ3L1dtBJ83XFG5tFClzhk7XiqCK7vHTRqTO+Jw55lqHaFM07 SNivzNEUrgsD5luiztKEdStLv0mLbKRr5NX+VCmdw8+RRXRUepLTqFjyzmtToMros2w== 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=jfBHJ1Pr; 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 09739606A31C for ; Tue, 10 Nov 2026 01:14:06 +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=jfBHJ1Pr Received: by smtp.kernel.org (Postfix) with ESMTPSA id BB1971F0089F; Tue, 10 Nov 2026 01:14:05 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1794273246; bh=0erLcdDfB3B910fHzg9R2k7tdGf2oO8vvq/0TsBK3JM=; h=From:To:Cc:Subject:Date; b=jfBHJ1PriRs4GuXpLh4Zqyn8ZNC16x1kWWdTPOe0pVLPHXb2POYdpi6zp0SNj4dp4 OcBllctFsB3EokLXcefr+BPAwu6OOUUlVUhdWXg673KBQx/43SDOY4SvGDcaeH0hho 4HoSOIkgrD/4FOuXngXmSJd4Q81nki/jXNuFSS8d/yg007KJFcfJihadAZX1gMuEzB dCi7GPE5qXZdd9vYfHoHZA4MoZRlSKTKbfqIsDhUi2pix7uGf+p7BntEIXav8i4BtG rQdT8liwQrVDHid11LgXZuCdzE9FZJFBN0YDOL9goBuipBh3QSHjVfcquNIuUJbY4U 1WJwGod4z3ufw== 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 6.6-stable tree Date: Mon, 9 Nov 2026 20:14:04 -0500 Message-ID: <20261109201404-failed-6.6-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 6.6-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-6.6.y git checkout FETCH_HEAD git cherry-pick -x b1ee87802111156e27557e82acc31fa7dfc76e2a # git commit -s git send-email --to '' --in-reply-to '20261109201404-failed-6.6-b1ee87802111@kernel.org' --subject-prefix 'PATCH 6.6.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