linux-kernel - Re: [PATCH v17 15/15] Documentation: prctl/seccomp

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: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CBA9C094.3CC91%ware@linux.intel.com>
Date:	Tue, 10 Apr 2012 10:49:41 -0700
From:	Ryan Ware <ware@...ux.intel.com>
To:	Will Drewry <wad@...omium.org>,
	Markus Gutschke <markus@...omium.org>,
	Andrew Morton <akpm@...ux-foundation.org>
CC:	<linux-kernel@...r.kernel.org>,
	<linux-security-module@...r.kernel.org>,
	<linux-arch@...r.kernel.org>, <linux-doc@...r.kernel.org>,
	<kernel-hardening@...ts.openwall.com>, <netdev@...r.kernel.org>,
	<x86@...nel.org>, <arnd@...db.de>, <davem@...emloft.net>,
	<hpa@...or.com>, <mingo@...hat.com>, <oleg@...hat.com>,
	<peterz@...radead.org>, <rdunlap@...otime.net>,
	<mcgrathr@...omium.org>, <tglx@...utronix.de>, <luto@....edu>,
	<eparis@...hat.com>, <serge.hallyn@...onical.com>,
	<djm@...drot.org>, <scarybeasts@...il.com>, <indan@....nu>,
	<pmoore@...hat.com>, <corbet@....net>, <eric.dumazet@...il.com>,
	<coreyb@...ux.vnet.ibm.com>, <keescook@...omium.org>,
	<jmorris@...ei.org>
Subject: Re: [PATCH v17 15/15] Documentation: prctl/seccomp_filter



On 4/9/12 3:47 PM, "Will Drewry" <wad@...omium.org> wrote:

>On Mon, Apr 9, 2012 at 3:58 PM, Ryan Ware <ware@...ux.intel.com> wrote:
>>
>> On 4/9/12 1:47 PM, "Markus Gutschke" <markus@...omium.org> wrote:
>>
>>>No matter what you do, please leave the samples accessible somewhere.
>>>They proved incredibly useful in figuring out how the API works. I am
>>>sure, other developers are going to appreciate them as well.
>>>
>>>Alternatively, if you don't want to include the samples with the
>>>kernel sources, figure out how you can include a sample in the
>>>official manual page for prctl().
>>>
>>
>> I second this!  They are extremely useful.
>>
>> Ryan
>
>In that case, would it make sense to put up a separate tools/testing
>patch and leave samples where they lie? (I'd _love_ to keep this patch
>series from acquiring another 1000 lines, but either way works :)
>
>My current tester and harness lives here:
>  https://github.com/redpig/seccomp/blob/master/tests/
>and the licensing can be sorted out prior to a patch mail.

I have absolutely no problems with that solution.  Availability is the
important thing.

Ryan


--
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/