From: Miroslav Benes <mbenes@suse.cz>
To: Michael Vetter <mvetter@suse.com>
Cc: linux-kselftest@vger.kernel.org, live-patching@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 3/3] selftests: livepatch: test livepatching a kprobed function
Date: Fri, 27 Sep 2024 14:54:43 +0200 (CEST) [thread overview]
Message-ID: <alpine.LSU.2.21.2409271453340.15317@pobox.suse.cz> (raw)
In-Reply-To: <20240920115631.54142-4-mvetter@suse.com>
Hi,
On Fri, 20 Sep 2024, Michael Vetter wrote:
> +# Kprobe a function and verify that we can't livepatch that same function
> +# when it uses a post_handler since only one IPMODIFY maybe be registered
> +# to any given function at a time.
> +
> +start_test "livepatch interaction with kprobed function with post_handler"
> +
> +echo 1 > /sys/kernel/debug/kprobes/enabled
opencoded here again.
The rest looks good to me.
Miroslav
next prev parent reply other threads:[~2024-09-27 12:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-20 11:56 [PATCH v3 0/3] selftests: livepatch: test livepatching a kprobed function Michael Vetter
2024-09-20 11:56 ` [PATCH v3 1/3] selftests: livepatch: rename KLP_SYSFS_DIR to SYSFS_KLP_DIR Michael Vetter
2024-09-27 12:41 ` Miroslav Benes
2024-09-20 11:56 ` [PATCH v3 2/3] selftests: livepatch: save and restore kprobe state Michael Vetter
2024-09-27 12:49 ` Miroslav Benes
2024-09-20 11:56 ` [PATCH v3 3/3] selftests: livepatch: test livepatching a kprobed function Michael Vetter
2024-09-27 12:54 ` Miroslav Benes [this message]
2024-09-23 14:45 ` [PATCH v3 0/3] " Marcos Paulo de Souza
2024-09-23 16:16 ` Shuah Khan
2024-09-24 9:21 ` Petr Mladek
2024-09-24 9:17 ` Petr Mladek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LSU.2.21.2409271453340.15317@pobox.suse.cz \
--to=mbenes@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=mvetter@suse.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox