Messages in this thread | | | Date | Tue, 17 Jun 2008 19:34:11 +0200 | From | Andrea Arcangeli <> | Subject | Re: PR_SET_SECCOMP and PR_GET_SECCOMP doc (and bug?) |
| |
On Tue, Jun 17, 2008 at 12:12:14PM -0400, Valdis.Kletnieks@vt.edu wrote: > On Tue, 17 Jun 2008 15:32:29 +0200, Michael Kerrisk said: > > On Mon, Jun 16, 2008 at 6:25 PM, Andrea Arcangeli <andrea@qumranet.com> wrote: > > > On Mon, Jun 16, 2008 at 02:15:13PM +0200, Michael Kerrisk wrote: > > > >> PR_GET_SECCOMP (since Linux 2.6.23) > > >> Return the secure computing mode of the calling thread. > > >> Not very useful: if the caller is not in secure computing > > >> mode, this operation returns 0; if the caller is in secure > > >> computing mode, then the prctl() call will cause a SIGKILL > > >> signal to be sent to the process. This operation is only > > >> available if the kernel is configured with CONFIG_SECCOMP > > >> enabled. > > Would it make sense to change the text to read "Not very useful for the > current implementation of mode=1" and/or add that it may be useful for
Yes, makes sense to me ;).
| |