From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alexei Starovoitov Subject: Re: linux-next: manual merge of the security tree with the net-next tree Date: Sun, 3 Aug 2014 23:30:35 -0700 Message-ID: References: <20140804162633.2d2e8604@canb.auug.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: Received: from mail-wi0-f177.google.com ([209.85.212.177]:46628 "EHLO mail-wi0-f177.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751053AbaHDGah (ORCPT ); Mon, 4 Aug 2014 02:30:37 -0400 Received: by mail-wi0-f177.google.com with SMTP id ho1so4359464wib.10 for ; Sun, 03 Aug 2014 23:30:35 -0700 (PDT) In-Reply-To: <20140804162633.2d2e8604@canb.auug.org.au> Sender: linux-next-owner@vger.kernel.org List-ID: To: Stephen Rothwell Cc: James Morris , David Miller , Network Development , linux-next@vger.kernel.org, LKML , Kees Cook On Sun, Aug 3, 2014 at 11:26 PM, Stephen Rothwell wrote: > Hi James, > > Today's linux-next merge of the security tree got a conflict in > kernel/seccomp.c between commit 7ae457c1e5b4 ("net: filter: split > 'struct sk_filter' into socket and bpf parts") from the net-next tree > and commits c8bee430dc52 ("seccomp: split filter prep from check and > apply") and 3ba2530cc06e ("seccomp: allow mode setting across threads") > from the security tree. > > I fixed it up (I hope - see below) and can carry the fix as necessary > (no action is required). Looks correct. Thanks. Will double check during merge window.