From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 2EDAD492537; Sat, 28 Feb 2026 17:44:24 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1772300664; cv=none; b=JsUBNLBpZ68wBdtHzO1EglwiBRLs/NvyAZCUsTMULuPbDFaBIbgZL5XaJj4n0Q/ZCMizTcHdIDzON1E4iOQ+2WIz39i5vl44OgNiboSLRNaAxt1f0696Fj4RruhrFx/14ABOS25eaQiAbhqadjvIWOy+8+1o+6lY/++GA8ypBuk= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1772300664; c=relaxed/simple; bh=l6graGhs00TKyzQLpbf68cfiC+x52l/KmoX1tNaXKPE=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version; b=Z+Gg+oATAqeFwEAI5p2MI8ljrLZzQT0X/+00ogLziC52sQ9zbKK8yEAS12NPo4V62QLYtcMHPlVJBzSqNvsHqEOEGbBEo2UntMPNXNYUcP9Cn2Ex+KbEFmLYMW+3tUBYxr53Z4XptEeFQT6E1nDod0JVY/an+UnMHNSinILXhe0= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=kCKXmY32; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="kCKXmY32" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 3AAE9C116D0; Sat, 28 Feb 2026 17:44:23 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1772300664; bh=l6graGhs00TKyzQLpbf68cfiC+x52l/KmoX1tNaXKPE=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=kCKXmY32G/PoOXBn4L62OS3iVA+azj7WYaiVal6b3xvmV8NMa190WNTyQfjZ9xjaw YZ/mjfkpFLwZUnseSK874Kl6H4SbkRktYJ+vS1jz+Q9YBSbu1kr/xnBqHCq8eR6RG+ KYIXHqzryhZGyYKwCAye0JWdTcB4SthN0PQpfzETVt7sfu3NrhLMk3Xqw+Zn7gJtRs Yvyf62rdt9qpkTFfqN57uWAK5Z+lXBwJGVEzOSQpvFlXT/h/M5aXg7QlR5lr1mUOMc JmdiPa4o4YcRQNccv/ohgvngHseLyxMuCN1GedDO97ta6eSf8AAKK4d2x9nY8lDJW1 PrBRCPNLTzzsA== From: Sasha Levin To: linux-kernel@vger.kernel.org, stable@vger.kernel.org Cc: Deepanshu Kartikey , syzbot+d8d4c31d40f868eaea30@syzkaller.appspotmail.com, Uladzislau Rezki , Hillf Danton , Andrew Morton , Sasha Levin Subject: [PATCH 6.19 701/844] mm/vmalloc: prevent RCU stalls in kasan_release_vmalloc_node Date: Sat, 28 Feb 2026 12:30:14 -0500 Message-ID: <20260228173244.1509663-702-sashal@kernel.org> X-Mailer: git-send-email 2.51.0 In-Reply-To: <20260228173244.1509663-1-sashal@kernel.org> References: <20260228173244.1509663-1-sashal@kernel.org> Precedence: bulk X-Mailing-List: stable@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-stable: review X-Patchwork-Hint: Ignore Content-Transfer-Encoding: 8bit From: Deepanshu Kartikey [ Upstream commit 5747435e0fd474c24530ef1a6822f47e7d264b27 ] When CONFIG_PAGE_OWNER is enabled, freeing KASAN shadow pages during vmalloc cleanup triggers expensive stack unwinding that acquires RCU read locks. Processing a large purge_list without rescheduling can cause the task to hold CPU for extended periods (10+ seconds), leading to RCU stalls and potential OOM conditions. The issue manifests in purge_vmap_node() -> kasan_release_vmalloc_node() where iterating through hundreds or thousands of vmap_area entries and freeing their associated shadow pages causes: rcu: INFO: rcu_preempt detected stalls on CPUs/tasks: rcu: Tasks blocked on level-0 rcu_node (CPUs 0-1): P6229/1:b..l ... task:kworker/0:17 state:R running task stack:28840 pid:6229 ... kasan_release_vmalloc_node+0x1ba/0xad0 mm/vmalloc.c:2299 purge_vmap_node+0x1ba/0xad0 mm/vmalloc.c:2299 Each call to kasan_release_vmalloc() can free many pages, and with page_owner tracking, each free triggers save_stack() which performs stack unwinding under RCU read lock. Without yielding, this creates an unbounded RCU critical section. Add periodic cond_resched() calls within the loop to allow: - RCU grace periods to complete - Other tasks to run - Scheduler to preempt when needed The fix uses need_resched() for immediate response under load, with a batch count of 32 as a guaranteed upper bound to prevent worst-case stalls even under light load. Link: https://lkml.kernel.org/r/20260112103612.627247-1-kartikey406@gmail.com Signed-off-by: Deepanshu Kartikey Reported-by: syzbot+d8d4c31d40f868eaea30@syzkaller.appspotmail.com Closes: https://syzkaller.appspot.com/bug?extid=d8d4c31d40f868eaea30 Link: https://lore.kernel.org/all/20260112084723.622910-1-kartikey406@gmail.com/T/ [v1] Suggested-by: Uladzislau Rezki Reviewed-by: Uladzislau Rezki (Sony) Cc: Hillf Danton Cc: Signed-off-by: Andrew Morton Signed-off-by: Sasha Levin --- mm/vmalloc.c | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/mm/vmalloc.c b/mm/vmalloc.c index e286c2d2068cb..ea24ee957605e 100644 --- a/mm/vmalloc.c +++ b/mm/vmalloc.c @@ -2268,11 +2268,14 @@ decay_va_pool_node(struct vmap_node *vn, bool full_decay) reclaim_list_global(&decay_list); } +#define KASAN_RELEASE_BATCH_SIZE 32 + static void kasan_release_vmalloc_node(struct vmap_node *vn) { struct vmap_area *va; unsigned long start, end; + unsigned int batch_count = 0; start = list_first_entry(&vn->purge_list, struct vmap_area, list)->va_start; end = list_last_entry(&vn->purge_list, struct vmap_area, list)->va_end; @@ -2282,6 +2285,11 @@ kasan_release_vmalloc_node(struct vmap_node *vn) kasan_release_vmalloc(va->va_start, va->va_end, va->va_start, va->va_end, KASAN_VMALLOC_PAGE_RANGE); + + if (need_resched() || (++batch_count >= KASAN_RELEASE_BATCH_SIZE)) { + cond_resched(); + batch_count = 0; + } } kasan_release_vmalloc(start, end, start, end, KASAN_VMALLOC_TLB_FLUSH); -- 2.51.0