linux-kernel - Re: [PATCH v5 3/3] selftests: livepatch: test livepatching a kprobed function

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.LSU.2.21.2410221407430.13912@pobox.suse.cz>
Date: Tue, 22 Oct 2024 14:08:11 +0200 (CEST)
From: Miroslav Benes <mbenes@...e.cz>
To: Michael Vetter <mvetter@...e.com>
cc: linux-kselftest@...r.kernel.org, live-patching@...r.kernel.org, 
    linux-kernel@...r.kernel.org
Subject: Re: [PATCH v5 3/3] selftests: livepatch: test livepatching a kprobed
 function

On Thu, 17 Oct 2024, Michael Vetter wrote:

> The test proves that a function that is being kprobed and uses a
> post_handler cannot be livepatched.
> 
> Only one ftrace_ops with FTRACE_OPS_FL_IPMODIFY set may be registered
> to any given function at a time.
> 
> Note that the conflicting kprobe could not be created using the
> tracefs interface, see Documentation/trace/kprobetrace.rst.
> This interface uses only the pre_handler(), see alloc_trace_kprobe().
> But FTRACE_OPS_FL_IPMODIFY is used only when the kprobe is using a
> post_handler, see arm_kprobe_ftrace().
> 
> Signed-off-by: Michael Vetter <mvetter@...e.com>

Nice test.

Reviewed-by: Miroslav Benes <mbenes@...e.cz>

Thank you,
Miroslav