Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: "Edgecombe, Rick P" <rick.p.edgecombe@intel.com>
To: "aleksey.oladko@virtuozzo.com" <aleksey.oladko@virtuozzo.com>,
	"ptikhomirov@virtuozzo.com" <ptikhomirov@virtuozzo.com>
Cc: "dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
	"x86@kernel.org" <x86@kernel.org>, "bp@alien8.de" <bp@alien8.de>,
	"hpa@zytor.com" <hpa@zytor.com>,
	"shuah@kernel.org" <shuah@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-kselftest@vger.kernel.org"
	<linux-kselftest@vger.kernel.org>,
	"tglx@kernel.org" <tglx@kernel.org>,
	"mingo@redhat.com" <mingo@redhat.com>
Subject: Re: [PATCH] selftests: x86: test_shadow_stack: return KSFT_SKIP when test is skipped
Date: Fri, 20 Mar 2026 17:23:02 +0000	[thread overview]
Message-ID: <242ac7e2587f510436d68dccf2877e03e311a75e.camel@intel.com> (raw)
In-Reply-To: <3205f6e7-bf02-4fb4-ab03-278447c17f70@virtuozzo.com>

On Fri, 2026-03-20 at 10:52 +0100, Pavel Tikhomirov wrote:
>         if (ARCH_PRCTL(ARCH_SHSTK_ENABLE, ARCH_SHSTK_SHSTK)) {
> -               printf("[SKIP]\tCould not re-enable Shadow stack\n");
> +               printf("[FAIL]\tCould not re-enable Shadow stack\n");
>                 return 1;
>         }
>  
>         if (ARCH_PRCTL(ARCH_SHSTK_ENABLE, ARCH_SHSTK_WRSS)) {
> -               printf("[SKIP]\tCould not enable WRSS\n");
> +               printf("[FAIL]\tCould not enable WRSS\n");
>                 ret = 1;
>                 goto out;
>         }
> @@ -1057,6 +1061,7 @@ int main(int argc, char *argv[])
>         if (test_ptrace()) {
>                 ret = 1;
>                 printf("[FAIL]\tptrace test\n");
> +               goto out;
>         }

Seems fine. The rest of the test could continue, but it's probably better to
have everything match. This whole function could be cleaned up actually, to be
more understandable and cleaner, so don't want to dig any further.

>  
>         if (test_32bit()) {

The rest looks good, thanks!

      reply	other threads:[~2026-03-20 17:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-01  1:47 [PATCH] selftests: x86: test_shadow_stack: return KSFT_SKIP when test is skipped Aleksei Oladko
2026-03-15 19:08 ` Aleksei Oladko
2026-03-19 16:38 ` Pavel Tikhomirov
2026-03-19 17:42   ` Edgecombe, Rick P
2026-03-20  9:52     ` Pavel Tikhomirov
2026-03-20 17:23       ` Edgecombe, Rick P [this message]

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=242ac7e2587f510436d68dccf2877e03e311a75e.camel@intel.com \
    --to=rick.p.edgecombe@intel.com \
    --cc=aleksey.oladko@virtuozzo.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=ptikhomirov@virtuozzo.com \
    --cc=shuah@kernel.org \
    --cc=tglx@kernel.org \
    --cc=x86@kernel.org \
    /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