[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20210702151927.263402-1-rodrigo@kinvolk.io>
Date: Fri, 2 Jul 2021 17:19:27 +0200
From: Rodrigo Campos <rodrigo@...volk.io>
To: Kees Cook <keescook@...omium.org>,
Andy Lutomirski <luto@...capital.net>,
Will Drewry <wad@...omium.org>, linux-kernel@...r.kernel.org,
containers@...ts.linux.dev
Cc: Alban Crequy <alban@...volk.io>,
Mauricio Vásquez Bernal <mauricio@...volk.io>,
Sargun Dhillon <sargun@...gun.me>,
Rodrigo Campos <rodrigo@...volk.io>,
Christian Brauner <christian.brauner@...ntu.com>
Subject: [PATCH] Documentation: seccomp: Fix typo in user notification
The close on exec flag is O_CLOEXEC, not O_EXEC. This patch just fixes
the typo.
Suggested-by: Christian Brauner <christian.brauner@...ntu.com>
Signed-off-by: Rodrigo Campos <rodrigo@...volk.io>
---
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 d61219889e49..539e9d4a4860 100644
--- a/Documentation/userspace-api/seccomp_filter.rst
+++ b/Documentation/userspace-api/seccomp_filter.rst
@@ -263,7 +263,7 @@ Userspace can also add file descriptors to the notifying process via
``ioctl(SECCOMP_IOCTL_NOTIF_ADDFD)``. The ``id`` member of
``struct seccomp_notif_addfd`` should be the same ``id`` as in
``struct seccomp_notif``. The ``newfd_flags`` flag may be used to set flags
-like O_EXEC on the file descriptor in the notifying process. If the supervisor
+like O_CLOEXEC on the file descriptor in the notifying process. If the supervisor
wants to inject the file descriptor with a specific number, the
``SECCOMP_ADDFD_FLAG_SETFD`` flag can be used, and set the ``newfd`` member to
the specific number to use. If that file descriptor is already open in the
--
2.30.2
Powered by blists - more mailing lists