linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [PATCH v1] seccomp: Fix documentation
@ 2016-09-20 17:39 Mickaël Salaün
  2016-10-15 16:31 ` Mickaël Salaün
  0 siblings, 1 reply; 3+ messages in thread
From: Mickaël Salaün @ 2016-09-20 17:39 UTC (permalink / raw)
  To: linux-kernel
  Cc: Mickaël Salaün, Andy Lutomirski, James Morris,
	Kees Cook, Will Drewry

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.
  */
-- 
2.9.3

^ permalink raw reply related	[flat|nested] 3+ messages in thread

* Re: [PATCH v1] seccomp: Fix documentation
  2016-09-20 17:39 [PATCH v1] seccomp: Fix documentation Mickaël Salaün
@ 2016-10-15 16:31 ` Mickaël Salaün
  2016-10-18 20:29   ` Kees Cook
  0 siblings, 1 reply; 3+ messages in thread
From: Mickaël Salaün @ 2016-10-15 16:31 UTC (permalink / raw)
  To: linux-kernel; +Cc: Andy Lutomirski, James Morris, Kees Cook, Will Drewry


[-- 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 --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [PATCH v1] seccomp: Fix documentation
  2016-10-15 16:31 ` Mickaël Salaün
@ 2016-10-18 20:29   ` Kees Cook
  0 siblings, 0 replies; 3+ messages in thread
From: Kees Cook @ 2016-10-18 20:29 UTC (permalink / raw)
  To: Mickaël Salaün; +Cc: LKML, Andy Lutomirski, James Morris, Will Drewry

On Sat, Oct 15, 2016 at 9:31 AM, Mickaël Salaün <mic@digikod.net> wrote:
> 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>

Ah, sorry, this got lost in my inbox. :)

Acked-by: Kees Cook <keescook@chromium.org>

-Kees

>> ---
>>  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.
>>   */
>>
>



-- 
Kees Cook
Nexus Security

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2016-10-18 20:29 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-09-20 17:39 [PATCH v1] seccomp: Fix documentation Mickaël Salaün
2016-10-15 16:31 ` Mickaël Salaün
2016-10-18 20:29   ` Kees Cook

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).