From: Valdis.Kletnieks@vt.edu
To: Michael Kerrisk <mtk.manpages@googlemail.com>
Cc: Andrea Arcangeli <andrea@qumranet.com>,
Ivana Varekova <varekova@redhat.com>,
lkml <linux-kernel@vger.kernel.org>,
linux-man@vger.kernel.org
Subject: Re: PR_SET_SECCOMP and PR_GET_SECCOMP doc (and bug?)
Date: Tue, 17 Jun 2008 12:12:14 -0400 [thread overview]
Message-ID: <18697.1213719134@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Tue, 17 Jun 2008 15:32:29 +0200." <cfd18e0f0806170632p27a5ccd2obadaf0dfd4ce64aa@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 910 bytes --]
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
future modes that allow prctl() modes other than 1?
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
next prev parent reply other threads:[~2008-06-17 16:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-16 12:15 Michael Kerrisk
2008-06-16 16:25 ` Andrea Arcangeli
2008-06-17 13:32 ` Michael Kerrisk
2008-06-17 16:12 ` Valdis.Kletnieks [this message]
2008-06-17 17:34 ` Andrea Arcangeli
2008-06-17 17:59 ` Michael Kerrisk
2008-06-17 17:35 ` Andrea Arcangeli
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=18697.1213719134@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=andrea@qumranet.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@googlemail.com \
--cc=varekova@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®