From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (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 D3F483C7E1D for ; Thu, 6 Aug 2026 17:02:20 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1786035743; cv=none; b=U9z7k+c3G5CfUlw/Se6f4h/g9H8rwUOjP8wBJF28zv6xZ6d0vRXyftRoBHMjUpAVfIXTLcmZ4l6NBFBcFqW/IFOSxhs6PXmmpE4ygaufg8w2bpdW/pEBcUqfJwwXaYK8XsRMsdsJS3O1i7Bqf/FFbLfPozmkmIdQNf4opELbou0= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1786035743; c=relaxed/simple; bh=+2VixsZKUpNDDm42DWYcB8nMpM9K/MUnKs+9qy7O3pw=; h=Date:From:To:cc:Subject:In-Reply-To:Message-ID:References: MIME-Version:Content-Type; b=jt0jamUqLpKXeIBVxz8rI4WjT1c9j74wB1xUwvBCevlKpPbG6Vm3sN9Axk0cTZmrRfhzts7uQ6itf3FCtwBnzBX7qzHp3iErHG53r2GtP88kAbdGQsPSC9CJ12sTMFpaLdU/u2aoxcLfyR8s0BVqY3Jys3+ZTvfBUAWK1+SgSpM= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=gNO5ZwQ0; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="gNO5ZwQ0" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 5FA031F000E9; Thu, 6 Aug 2026 17:02:18 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1786035739; bh=OXAQKFIVVBbXnWv8484Zj8obP/yiaKmVTqPj7jB+Q/Y=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=gNO5ZwQ0z1emNmNw7dGtvsia/4vsFxCFFwfLJOdUtuda28fIvY0ldMPjcZ16rf8Kt dG+1Axcl0PALGVZ9AXKWLGIPAO2E9FoNqfMyHeahTieqVDJndWEga8PLPtdLYov93n 4jldhNWnDtVooT+W6XKTnzRxiAovXHBBToB+py4jEzHDFI0XiGNmW/myXJ7laq2zjF YOJoYLI6R7t0HL7sIshOMECX3+J4L7DwLXN8H6g7r5c26O7io7riPCxO4F8PhOUvhP ktJbKzPyo1ZnpxPZkKmNf33NRCrB+x6oLl3RYd6Kspg3AjeQgpEt6nbm0EFVs0wcXt VB59zQlflqvBg== Date: Thu, 6 Aug 2026 11:02:15 -0600 (MDT) From: Paul Walmsley To: Rui Qi cc: Paul Walmsley , Palmer Dabbelt , Albert Ou , Alexandre Ghiti , Nam Cao , Thomas Gleixner , Zong Li , Ryan Roberts , Deepak Gupta , linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v2] riscv: kprobes: Prevent probes in breakpoint handlers In-Reply-To: <20260806043807.2583001-1-qirui.001@bytedance.com> Message-ID: <5b07524c-1b93-22a7-ed9b-037d499a5b3f@kernel.org> References: <20260806043807.2583001-1-qirui.001@bytedance.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII On Thu, 6 Aug 2026, Rui Qi wrote: > The ftrace selftest multiple_kprobes.tc registers kprobe events on > the first 256 text symbols from /proc/kallsyms. If handle_break() is > selected as a probe target on RISC-V, the breakpoint exception path > can trap again before it reaches the kprobe breakpoint handler. That > recursively enters do_trap_break() and can make the system > unresponsive. > > Mark handle_break() and its local probe dispatch helpers as nokprobe > symbols so they are added to the kprobe blacklist, matching other > low-level breakpoint exception paths. > > Signed-off-by: Rui Qi > Reviewed-by: Nam Cao Thanks, queued for v7.3. - Paul