public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Oleg Nesterov <oleg@redhat.com>
To: Kees Cook <kees@kernel.org>,
	Andy Lutomirski <luto@amacapital.net>,
	Will Drewry <wad@chromium.org>
Cc: linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] selftests/seccomp: Add hard-coded __NR_uretprobe for x86_64
Date: Fri, 3 Apr 2026 15:29:19 +0200	[thread overview]
Message-ID: <ac_Ar-3u6mSwjl0Z@redhat.com> (raw)
In-Reply-To: <ac-7vdQNYdSGqcp-@redhat.com>

On 04/03, Oleg Nesterov wrote:
>
> This complements the commit 18f7686a1ce6 ("selftests/seccomp:
> Add hard-coded __NR_uretprobe for x86_64").

Yes, and I forgot to change the subject line ;)

Please ignore, will resend in reply to this email.

Oleg.

> Signed-off-by: Oleg Nesterov <oleg@redhat.com>
> ---
>  tools/testing/selftests/seccomp/seccomp_bpf.c | 6 ++++++
>  1 file changed, 6 insertions(+)
> 
> diff --git a/tools/testing/selftests/seccomp/seccomp_bpf.c b/tools/testing/selftests/seccomp/seccomp_bpf.c
> index 32e2d4df397b..358b6c65e120 100644
> --- a/tools/testing/selftests/seccomp/seccomp_bpf.c
> +++ b/tools/testing/selftests/seccomp/seccomp_bpf.c
> @@ -170,6 +170,12 @@ struct seccomp_data {
>  # endif
>  #endif
>  
> +#ifndef __NR_uprobe
> +# if defined(__x86_64__)
> +#  define __NR_uprobe 336
> +# endif
> +#endif
> +
>  #ifndef SECCOMP_SET_MODE_STRICT
>  #define SECCOMP_SET_MODE_STRICT 0
>  #endif
> -- 
> 2.52.0
> 


  reply	other threads:[~2026-04-03 13:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-03 13:08 [PATCH] selftests/seccomp: Add hard-coded __NR_uretprobe for x86_64 Oleg Nesterov
2026-04-03 13:29 ` Oleg Nesterov [this message]
2026-04-03 13:30 ` [PATCH] selftests/seccomp: Add hard-coded __NR_uprobe " Oleg Nesterov
2026-04-03 15:42   ` (subset) " Kees Cook

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=ac_Ar-3u6mSwjl0Z@redhat.com \
    --to=oleg@redhat.com \
    --cc=kees@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=wad@chromium.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