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: <560EA006.2000306@iogearbox.net>
Date:	Fri, 02 Oct 2015 17:17:26 +0200
From:	Daniel Borkmann <daniel@...earbox.net>
To:	Tycho Andersen <tycho.andersen@...onical.com>
CC:	davem@...emloft.net, netdev@...r.kernel.org,
	Pavel Emelyanov <xemul@...allels.com>,
	Kees Cook <keescook@...omium.org>,
	Andy Lutomirski <luto@...capital.net>,
	Alexei Starovoitov <ast@...mgrid.com>
Subject: Re: [PATCH net-next] bpf, seccomp: prepare for upcoming criu support

On 10/02/2015 05:06 PM, Tycho Andersen wrote:
...
>> Cc: Pavel Emelyanov <xemul@...allels.com>
>> Cc: Kees Cook <keescook@...omium.org>
>> Cc: Andy Lutomirski <luto@...capital.net>
>> Cc: Alexei Starovoitov <ast@...mgrid.com>
>> ---
>>   This is in realtion to Tycho's latest patch set under [1]. The BPF
>>   handling is unfortunately not correct (triggering a crash on kernels
>>   that can set pages as ro).
>>
>>   This patch here provides a minimal, simple interface from BPF API side
>>   as a possible step forward, so that the focus can then be on seccomp
>>   side wrt criu. F.e., dumping could happen similarly as in Pavel's
>>   sk_get_filter().
>>
>>   I have tested/based this against net-next, but have no issues whether
>>   Kees wants to take it, or whether it should go through both trees to
>>   reduce merge issues as once the case with 0fc174dea545 ("ebpf: make
>>   internal bpf API independent of CONFIG_BPF_SYSCALL ifdefs").
>
> I'll send out a revised version of my set with Andy's comments later
> today and not include this patch. Let me know if I should do something
> differently.

Should be okay.

Please make sure to describe in your cover letter that your series builds
on top of ...

   http://patchwork.ozlabs.org/patch/525492/

... so that whoever takes the set eventually is aware of this.

Thanks again,
Daniel
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ