From: "Mickaël Salaün" <mic@digikod.net>
To: linux-kernel@vger.kernel.org
Cc: Andy Lutomirski <luto@amacapital.net>,
James Morris <jmorris@namei.org>,
Kees Cook <keescook@chromium.org>, Will Drewry <wad@chromium.org>
Subject: Re: [PATCH v1] seccomp: Fix documentation
Date: Sat, 15 Oct 2016 18:31:47 +0200 [thread overview]
Message-ID: <580259F3.5040309@digikod.net> (raw)
In-Reply-To: <20160920173947.8684-1-mic@digikod.net>
[-- Attachment #1.1: Type: text/plain, Size: 1607 bytes --]
Could someone push this please?
On 20/09/2016 19:39, Mickaël Salaün wrote:
> Fix struct seccomp_filter and seccomp_run_filters() signatures.
>
> Signed-off-by: Mickaël Salaün <mic@digikod.net>
> Cc: Andy Lutomirski <luto@amacapital.net>
> Cc: James Morris <jmorris@namei.org>
> Cc: Kees Cook <keescook@chromium.org>
> Cc: Will Drewry <wad@chromium.org>
> ---
> kernel/seccomp.c | 7 +++----
> 1 file changed, 3 insertions(+), 4 deletions(-)
>
> diff --git a/kernel/seccomp.c b/kernel/seccomp.c
> index 0db7c8a2afe2..494cba230ca0 100644
> --- a/kernel/seccomp.c
> +++ b/kernel/seccomp.c
> @@ -41,8 +41,7 @@
> * outside of a lifetime-guarded section. In general, this
> * is only needed for handling filters shared across tasks.
> * @prev: points to a previously installed, or inherited, filter
> - * @len: the number of instructions in the program
> - * @insnsi: the BPF program instructions to evaluate
> + * @prog: the BPF program to evaluate
> *
> * seccomp_filter objects are organized in a tree linked via the @prev
> * pointer. For any task, it appears to be a singly-linked list starting
> @@ -168,8 +167,8 @@ static int seccomp_check_filter(struct sock_filter *filter, unsigned int flen)
> }
>
> /**
> - * seccomp_run_filters - evaluates all seccomp filters against @syscall
> - * @syscall: number of the current system call
> + * seccomp_run_filters - evaluates all seccomp filters against @sd
> + * @sd: optional seccomp data to be passed to filters
> *
> * Returns valid seccomp BPF response codes.
> */
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
next prev parent reply other threads:[~2016-10-15 16:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-20 17:39 [PATCH v1] seccomp: Fix documentation Mickaël Salaün
2016-10-15 16:31 ` Mickaël Salaün [this message]
2016-10-18 20:29 ` 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=580259F3.5040309@digikod.net \
--to=mic@digikod.net \
--cc=jmorris@namei.org \
--cc=keescook@chromium.org \
--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 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.