public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: Denis Efremov <efremov@linux.com>
Cc: Andy Lutomirski <luto@amacapital.net>,
	Will Drewry <wad@chromium.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] seccomp: Use current_pt_regs()
Date: Mon, 24 Aug 2020 09:34:27 -0700	[thread overview]
Message-ID: <202008240929.8DDED2B90@keescook> (raw)
In-Reply-To: <20200824125921.488311-1-efremov@linux.com>

On Mon, Aug 24, 2020 at 03:59:21PM +0300, Denis Efremov wrote:
> Modify seccomp_do_user_notification(), __seccomp_filter(),
> __secure_computing() to use current_pt_regs().

This looks okay. It seems some architectures have a separate
define for current_pt_regs(), though it's overlapped directly with
task_pt_regs(). I'm curious what the benefit of the change is?

-Kees

> 
> Signed-off-by: Denis Efremov <efremov@linux.com>
> ---
>  kernel/seccomp.c | 14 +++++++-------
>  1 file changed, 7 insertions(+), 7 deletions(-)
> 
> diff --git a/kernel/seccomp.c b/kernel/seccomp.c
> index 3ee59ce0a323..dc4eaa1d6002 100644
> --- a/kernel/seccomp.c
> +++ b/kernel/seccomp.c
> @@ -910,7 +910,7 @@ static int seccomp_do_user_notification(int this_syscall,
>  	if (flags & SECCOMP_USER_NOTIF_FLAG_CONTINUE)
>  		return 0;
>  
> -	syscall_set_return_value(current, task_pt_regs(current),
> +	syscall_set_return_value(current, current_pt_regs(),
>  				 err, ret);
>  	return -1;
>  }
> @@ -943,13 +943,13 @@ static int __seccomp_filter(int this_syscall, const struct seccomp_data *sd,
>  		/* Set low-order bits as an errno, capped at MAX_ERRNO. */
>  		if (data > MAX_ERRNO)
>  			data = MAX_ERRNO;
> -		syscall_set_return_value(current, task_pt_regs(current),
> +		syscall_set_return_value(current, current_pt_regs(),
>  					 -data, 0);
>  		goto skip;
>  
>  	case SECCOMP_RET_TRAP:
>  		/* Show the handler the original registers. */
> -		syscall_rollback(current, task_pt_regs(current));
> +		syscall_rollback(current, current_pt_regs());
>  		/* Let the filter pass back 16 bits of data. */
>  		seccomp_send_sigsys(this_syscall, data);
>  		goto skip;
> @@ -962,7 +962,7 @@ static int __seccomp_filter(int this_syscall, const struct seccomp_data *sd,
>  		/* ENOSYS these calls if there is no tracer attached. */
>  		if (!ptrace_event_enabled(current, PTRACE_EVENT_SECCOMP)) {
>  			syscall_set_return_value(current,
> -						 task_pt_regs(current),
> +						 current_pt_regs(),
>  						 -ENOSYS, 0);
>  			goto skip;
>  		}
> @@ -982,7 +982,7 @@ static int __seccomp_filter(int this_syscall, const struct seccomp_data *sd,
>  		if (fatal_signal_pending(current))
>  			goto skip;
>  		/* Check if the tracer forced the syscall to be skipped. */
> -		this_syscall = syscall_get_nr(current, task_pt_regs(current));
> +		this_syscall = syscall_get_nr(current, current_pt_regs());
>  		if (this_syscall < 0)
>  			goto skip;
>  
> @@ -1025,7 +1025,7 @@ static int __seccomp_filter(int this_syscall, const struct seccomp_data *sd,
>  			kernel_siginfo_t info;
>  
>  			/* Show the original registers in the dump. */
> -			syscall_rollback(current, task_pt_regs(current));
> +			syscall_rollback(current, current_pt_regs());
>  			/* Trigger a manual coredump since do_exit skips it. */
>  			seccomp_init_siginfo(&info, this_syscall, data);
>  			do_coredump(&info);
> @@ -1060,7 +1060,7 @@ int __secure_computing(const struct seccomp_data *sd)
>  		return 0;
>  
>  	this_syscall = sd ? sd->nr :
> -		syscall_get_nr(current, task_pt_regs(current));
> +		syscall_get_nr(current, current_pt_regs());
>  
>  	switch (mode) {
>  	case SECCOMP_MODE_STRICT:
> -- 
> 2.26.2
> 

-- 
Kees Cook

  reply	other threads:[~2020-08-24 16:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-24 12:59 [PATCH] seccomp: Use current_pt_regs() Denis Efremov
2020-08-24 16:34 ` Kees Cook [this message]
2020-08-24 18:03   ` Denis Efremov
2020-09-08 20:01 ` 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=202008240929.8DDED2B90@keescook \
    --to=keescook@chromium.org \
    --cc=efremov@linux.com \
    --cc=linux-kernel@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