Re: [PATCH 1/2] Documentation: seccomp: fix reST markup

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Mar 4, 2019 at 12:32 PM Jakub Wilk <jwilk@xxxxxxxxx> wrote:
>
> Signed-off-by: Jakub Wilk <jwilk@xxxxxxxxx>

Hah, whoops. Thanks!

Acked-by: Kees Cook <keescook@xxxxxxxxxxxx>

-Kees

> ---
>  Documentation/userspace-api/seccomp_filter.rst | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/userspace-api/seccomp_filter.rst b/Documentation/userspace-api/seccomp_filter.rst
> index b1b846d8a094..0f09a63ea923 100644
> --- a/Documentation/userspace-api/seccomp_filter.rst
> +++ b/Documentation/userspace-api/seccomp_filter.rst
> @@ -133,7 +133,7 @@ In precedence order, they are:
>         call.  If there is no tracer present, ``-ENOSYS`` is returned to
>         userland and the system call is not executed.
>
> -       A tracer will be notified if it requests ``PTRACE_O_TRACESECCOM``P
> +       A tracer will be notified if it requests ``PTRACE_O_TRACESECCOMP``
>         using ``ptrace(PTRACE_SETOPTIONS)``.  The tracer will be notified
>         of a ``PTRACE_EVENT_SECCOMP`` and the ``SECCOMP_RET_DATA`` portion of
>         the BPF program return value will be available to the tracer
> --
> 2.20.1
>


-- 
Kees Cook



[Index of Archives]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Linux FS]     [Yosemite Forum]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]     [Linux Resources]

  Powered by Linux