All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Bill Roberts" <bill.roberts@arm.com>
Cc: bpf@vger.kernel.org
Subject: Re: [PATCH v5 6/6] selftests/x86: add generic prctl shadow stack test
Date: Mon, 09 Nov 2026 18:46:40 +0000	[thread overview]
Message-ID: <sashiko-outbox-205437@kernel.org> (raw)
In-Reply-To: <20261109182758.252223-7-bill.roberts@arm.com>

Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [Low] selftests/x86: duplicate test_shadow_stack entry in
  TARGETS_C_64BIT_ONLY
--

commit 52e57f66207c4b662bab2432ff697c9236a6020d
Author: Bill Roberts <bill.roberts@arm.com>

selftests/x86: add generic prctl shadow stack test

This commit refactors the x86 shadow stack selftest into a shared
implementation and adds a test_shadow_stack_prctl entry point to exercise
the generic prctl() shadow stack operations alongside arch_prctl().

> diff --git a/tools/testing/selftests/x86/Makefile b/tools/testing/selftests/x86/Makefile
> index effbfe9b269f3..48c7459091614 100644
> --- a/tools/testing/selftests/x86/Makefile
> +++ b/tools/testing/selftests/x86/Makefile
> @@ -20,7 +20,7 @@ TARGETS_C_32BIT_ONLY := entry_from_vm86 test_syscall_vdso unwind_vdso \
>  			vdso_restorer
>  TARGETS_C_64BIT_ONLY := fsgsbase sysret_rip syscall_numbering \
>  			corrupt_xstate_header amx lam test_shadow_stack avx apx \
> -			sigframe_fpu_portability
> +			sigframe_fpu_portability test_shadow_stack test_shadow_stack_prctl

[Severity: Low]
Does adding test_shadow_stack here duplicate the existing entry on the
previous line of TARGETS_C_64BIT_ONLY?  Because BINARIES_64 and TEST_PROGS
expand TARGETS_C_64BIT_ONLY without deduplication, make warns about duplicate
target recipes for test_shadow_stack_64 and kselftest runs the binary twice.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261109182758.252223-1-bill.roberts@arm.com?part=6

      reply	other threads:[~2026-11-09 18:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-09 18:27 [PATCH v5 0/6] x86: Support shstk via prctl Bill Roberts
2026-11-09 18:27 ` [PATCH v5 1/6] selftests/x86: fix Makefile dependencies Bill Roberts
2026-11-09 18:27 ` [PATCH v5 2/6] selftests/x86: fix fork bug Bill Roberts
2026-11-09 18:36   ` sashiko-bot
2026-11-09 18:27 ` [PATCH v5 3/6] selftests/x86: add shadow stack lock test Bill Roberts
2026-11-09 18:35   ` sashiko-bot
2026-11-09 18:27 ` [PATCH v5 4/6] x86/shstk: support via prctl Bill Roberts
2026-11-09 18:52   ` sashiko-bot
2026-11-09 18:27 ` [PATCH v5 5/6] selftests/x86: support header files in extra-files Bill Roberts
2026-11-09 18:27 ` [PATCH v5 6/6] selftests/x86: add generic prctl shadow stack test Bill Roberts
2026-11-09 18:46   ` sashiko-bot [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=sashiko-outbox-205437@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=bill.roberts@arm.com \
    --cc=bpf@vger.kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.