lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Wed, 07 Jan 2015 13:41:39 +0100
From:	"Michael Kerrisk (man-pages)" <mtk.manpages@...il.com>
To:	Daniel Borkmann <dborkman@...hat.com>
CC:	mtk.manpages@...il.com, Kees Cook <keescook@...omium.org>,
	Linux API <linux-api@...r.kernel.org>,
	"linux-man@...r.kernel.org" <linux-man@...r.kernel.org>,
	lkml <linux-kernel@...r.kernel.org>,
	Will Drewry <wad@...omium.org>, ast@...mgrid.com
Subject: Re: Edited seccomp.2 man page for review [v2]

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/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ