Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752412AbaG1Xpm (ORCPT ); Mon, 28 Jul 2014 19:45:42 -0400 Received: from terminus.zytor.com ([198.137.202.10]:50654 "EHLO mail.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750840AbaG1Xpk (ORCPT ); Mon, 28 Jul 2014 19:45:40 -0400 Message-ID: <53D6E07F.7090806@zytor.com> Date: Mon, 28 Jul 2014 16:45:03 -0700 From: "H. Peter Anvin" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.7.0 MIME-Version: 1.0 To: Kees Cook CC: linux-arch , Linux MIPS Mailing List , Will Drewry , "x86@kernel.org" , LKML , Andy Lutomirski , linux-security-module , Oleg Nesterov , "linux-arm-kernel@lists.infradead.org" , Alexei Starovoitov Subject: Re: [PATCH v3 0/8] Two-phase seccomp and x86 tracing changes References: <53D68F91.4000106@zytor.com> <53D6DE1E.1060501@zytor.com> In-Reply-To: X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 07/28/2014 04:42 PM, Kees Cook wrote: > On Mon, Jul 28, 2014 at 4:34 PM, H. Peter Anvin wrote: >> On 07/28/2014 04:29 PM, Kees Cook wrote: >>> On Mon, Jul 28, 2014 at 10:59 AM, H. Peter Anvin wrote: >>>> On 07/23/2014 12:20 PM, Andy Lutomirski wrote: >>>>> >>>>> It looks like patches 1-4 have landed here: >>>>> >>>>> https://git.kernel.org/cgit/linux/kernel/git/kees/linux.git/log/?h=seccomp/fastpath >>>>> >>>>> hpa, what's the route forward for the x86 part? >>>>> >>>> >>>> I guess I should discuss this with Kees to figure out what makes most >>>> sense. In the meantime, could you address Oleg's question? >>> >>> Since the x86 parts depend on the seccomp parts, I'm happy if you >>> carry them instead of having them land from my tree. Otherwise I'm >>> open to how to coordinate timing. >>> >> >> You mean for me to carry the seccomp part as well? > > If that makes sense as far as the coordination, that's fine with me. > Otherwise I'm not sure how x86 can build without having the seccomp > changes in your tree. > Exactly. What I guess I'll do is set up a separate tip branch for this, pull your branch into it, and then put the x86 patches on top. Does that make sense for everyone? -hpa -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/