Merge tag 'armsoc-dt' of git://git.kernel.org/pub/scm/linux/kernel/git/soc/soc

[sfrench/cifs-2.6.git] / Documentation / userspace-api / seccomp_filter.rst

diff --git a/Documentation/userspace-api/seccomp_filter.rst b/Documentation/userspace-api/seccomp_filter.rst
index b1b846d8a0946de5e5540e322925bbc4da30d1f5..bd9165241b6c8970754c5ab7b84087b4eb251ba5 100644 (file)
--- a/Documentation/userspace-api/seccomp_filter.rst
+++ b/Documentation/userspace-api/seccomp_filter.rst
@@ -123,9 +123,9 @@ In precedence order, they are:
        to userland as the errno without executing the system call.
 
 ``SECCOMP_RET_USER_NOTIF``:
-    Results in a ``struct seccomp_notif`` message sent on the userspace
-    notification fd, if it is attached, or ``-ENOSYS`` if it is not. See below
-    on discussion of how to handle user notifications.
+       Results in a ``struct seccomp_notif`` message sent on the userspace
+       notification fd, if it is attached, or ``-ENOSYS`` if it is not. See
+       below on discussion of how to handle user notifications.
 
 ``SECCOMP_RET_TRACE``:
        When returned, this value will cause the kernel to attempt to
@@ -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