Linux Kernel Selftest development
 help / color / mirror / Atom feed
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 v4 1/3] selftests: livepatch: rename KLP_SYSFS_DIR to SYSFS_KLP_DIR
Date: Wed, 2 Oct 2024 17:23:27 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LSU.2.21.2410021720190.23724@pobox.suse.cz> (raw)
In-Reply-To: <20240930093308.65103-2-mvetter@suse.com>

Hi,

On Mon, 30 Sep 2024, Michael Vetter wrote:

> This naming makes more sense according to the directory structure.
> Especially when we later add more paths.
> 
> Signed-off-by: Michael Vetter <mvetter@suse.com>
> ---
>  tools/testing/selftests/livepatch/functions.sh | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/tools/testing/selftests/livepatch/functions.sh b/tools/testing/selftests/livepatch/functions.sh
> index fc4c6a016d38..50361fceff06 100644
> --- a/tools/testing/selftests/livepatch/functions.sh
> +++ b/tools/testing/selftests/livepatch/functions.sh
> @@ -6,7 +6,7 @@
>  
>  MAX_RETRIES=600
>  RETRY_INTERVAL=".1"	# seconds
> -KLP_SYSFS_DIR="/sys/kernel/livepatch"
> +SYSFS_KLP_DIR="/sys/kernel/livepatch"
>  
>  # Kselftest framework requirement - SKIP code is 4
>  ksft_skip=4
> @@ -322,7 +322,7 @@ function check_sysfs_rights() {
>  	local rel_path="$1"; shift
>  	local expected_rights="$1"; shift
>  
> -	local path="$KLP_SYSFS_DIR/$mod/$rel_path"
> +	local path="$SYSFS_KLP_DIR/$mod/$rel_path"
>  	local rights=$(/bin/stat --format '%A' "$path")
>  	if test "$rights" != "$expected_rights" ; then
>  		die "Unexpected access rights of $path: $expected_rights vs. $rights"
> @@ -338,7 +338,7 @@ function check_sysfs_value() {
>  	local rel_path="$1"; shift
>  	local expected_value="$1"; shift
>  
> -	local path="$KLP_SYSFS_DIR/$mod/$rel_path"
> +	local path="$SYSFS_KLP_DIR/$mod/$rel_path"
>  	local value=`cat $path`
>  	if test "$value" != "$expected_value" ; then
>  		die "Unexpected value in $path: $expected_value vs. $value"

I am sorry I was not explicit enough previously. There are still 
/sys/kernel/livepatch occurrences in tools/testing/selftest/livepatch/ 
which can be replaced with this new variable. They are there for quite 
some time but it would be really nice if you could replace them all to 
make it consistent since you are touching it.

Thank you,
Miroslav

  reply	other threads:[~2024-10-02 15:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-30  9:33 [PATCH v4 0/3] selftests: livepatch: test livepatching a kprobed function Michael Vetter
2024-09-30  9:33 ` [PATCH v4 1/3] selftests: livepatch: rename KLP_SYSFS_DIR to SYSFS_KLP_DIR Michael Vetter
2024-10-02 15:23   ` Miroslav Benes [this message]
2024-09-30  9:33 ` [PATCH v4 2/3] selftests: livepatch: save and restore kprobe state Michael Vetter
2024-09-30  9:33 ` [PATCH v4 3/3] selftests: livepatch: test livepatching a kprobed function Michael Vetter
2024-10-02 15:29   ` Miroslav Benes
2024-10-02 13:55 ` [PATCH v4 0/3] " Marcos Paulo de Souza

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.2410021720190.23724@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