From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Tyler Hicks <tyhicks-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
Kees Cook <keescook-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 0/4] Document new seccomp interfaces in Linux 4.14
Date: Thu, 9 Nov 2017 15:25:25 +0100 [thread overview]
Message-ID: <f49ff3da-c53a-e185-d994-00bc89b6a126@gmail.com> (raw)
In-Reply-To: <1508991102-13686-1-git-send-email-tyhicks-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
Hello Tyler,
On 10/26/2017 06:11 AM, Tyler Hicks wrote:
> This patchset adds documentation for most of the new user-facing features
> (/proc interfaces, SECCOMP_GET_ACTION_AVAIL operation, SECCOMP_FILTER_FLAG_LOG
> flag, SECCOMP_RET_LOG action) merged into Linux 4.14 (commit
> c0a3a64e723324ae6dda53214061a71de63808c3). All of these features have something
> to do with providing more flexible seccomp logging configuration except for the
> SECCOMP_GET_ACTION_AVAIL operation.
Thanks for this set! I've applied all of the patches, made a few very minor
tweaks, and pushed to Git.
But, I realize there's some pieces missing about audit logging.
Would you be able/willing to write a patch for the seccomp(2)
page describing the audit details?
> The remaining undocumented changes in 4.14 involve SECCOMP_RET_KILL being
> renamed to SECCOMP_RET_KILL_THREAD and the new SECCOMP_RET_KILL_PROCESS action.
> As I understand it, Kees Cook will be documenting those changes.
Kees, are you there ? ;-)
Cheers,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-11-09 14:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-26 4:11 [PATCH 0/4] Document new seccomp interfaces in Linux 4.14 Tyler Hicks
[not found] ` <1508991102-13686-1-git-send-email-tyhicks-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
2017-10-26 4:11 ` [PATCH 1/4] proc.5, seccomp.2: seccomp /proc interfaces Tyler Hicks
2017-10-26 4:11 ` [PATCH 2/4] seccomp.2: SECCOMP_GET_ACTION_AVAIL operation Tyler Hicks
2017-10-26 4:11 ` [PATCH 3/4] seccomp.2: SECCOMP_FILTER_FLAG_LOG flag Tyler Hicks
2017-10-26 4:11 ` [PATCH 4/4] seccomp.2: SECCOMP_RET_LOG action Tyler Hicks
2017-11-09 14:25 ` Michael Kerrisk (man-pages) [this message]
[not found] ` <f49ff3da-c53a-e185-d994-00bc89b6a126-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-11-09 18:10 ` [PATCH 0/4] Document new seccomp interfaces in Linux 4.14 Kees Cook
[not found] ` <CAGXu5j+qU4mwkMXkvgpKqWDxWga18EvN1T_8uieWnOOcKnd1+A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-11-09 19:18 ` Michael Kerrisk (man-pages)
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=f49ff3da-c53a-e185-d994-00bc89b6a126@gmail.com \
--to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=keescook-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=tyhicks-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org \
/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