mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Daniel Borkmann <dborkman@redhat.com>
Cc: mtk.manpages@gmail.com, Kees Cook <keescook@chromium.org>,
	Linux API <linux-api@vger.kernel.org>,
	"linux-man@vger.kernel.org" <linux-man@vger.kernel.org>,
	lkml <linux-kernel@vger.kernel.org>,
	Will Drewry <wad@chromium.org>,
	ast@plumgrid.com
Subject: Re: Edited seccomp.2 man page for review [v2]
Date: Wed, 07 Jan 2015 13:41:39 +0100	[thread overview]
Message-ID: <54AD2983.2060108@gmail.com> (raw)
In-Reply-To: <54AD2549.9040107@redhat.com>

On 01/07/2015 01:23 PM, Daniel Borkmann wrote:
> On 01/07/2015 12:53 PM, Michael Kerrisk (man-pages) wrote:
> ...
>> Still hoping to hear from Will Drewy regarding this FIXME in the
>> page source:
>>
>> .\" FIXME What is the significance of the line
>> .\"           ftest->code = BPF_LDX | BPF_W | BPF_ABS;
>> .\"       in kernel/seccomp.c::seccomp_check_filter()?
> 
> This came in from our rework via commit bd4cf0ed331a ("net: filter:
> rework/optimize internal BPF interpreter's instruction set"), and
> is kernel-internal only, and unused in classic BPF. It translates
> into A = *(u32 *) (ctx + K) and will basically load an offset from
> the populated seccomp_data (= ctx) to A. For the man-page itself
> it has therefore no relevance, hope that clarifies it.

Thanks, Daniel.

Okay -- that was the last hurdle. The page should go out with the 
next man-pages release.

Cheers,

Michael




-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/

      reply	other threads:[~2015-01-07 12:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-30 12:14 Michael Kerrisk (man-pages)
2014-12-30 17:16 ` Kees Cook
2014-12-30 19:45   ` Michael Kerrisk (man-pages)
2015-01-05 20:25     ` Kees Cook
2015-01-07 11:53       ` Michael Kerrisk (man-pages)
2015-01-07 12:23         ` Daniel Borkmann
2015-01-07 12:41           ` Michael Kerrisk (man-pages) [this message]

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=54AD2983.2060108@gmail.com \
    --to=mtk.manpages@gmail.com \
    --cc=ast@plumgrid.com \
    --cc=dborkman@redhat.com \
    --cc=keescook@chromium.org \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-man@vger.kernel.org \
    --cc=wad@chromium.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

Powered by JetHome