Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1161343AbbKTVGI (ORCPT ); Fri, 20 Nov 2015 16:06:08 -0500 Received: from mail-yk0-f182.google.com ([209.85.160.182]:33434 "EHLO mail-yk0-f182.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751895AbbKTVGF (ORCPT ); Fri, 20 Nov 2015 16:06:05 -0500 Date: Fri, 20 Nov 2015 16:06:02 -0500 From: Tejun Heo To: Pablo Neira Ayuso Cc: David Miller , kaber@trash.net, kadlec@blackhole.kfki.hu, lizefan@huawei.com, hannes@cmpxchg.org, netdev@vger.kernel.org, netfilter-devel@vger.kernel.org, coreteam@netfilter.org, cgroups@vger.kernel.org, linux-kernel@vger.kernel.org, kernel-team@fb.com, daniel@iogearbox.net, daniel.wagner@bmw-carit.de, nhorman@tuxdriver.com Subject: Re: [PATCHSET v2] netfilter, cgroup: implement xt_cgroup2 match Message-ID: <20151120210602.GD1574@mtj.duckdns.org> References: <1447959171-20749-1-git-send-email-tj@kernel.org> <20151120.135912.1506496112678349111.davem@davemloft.net> <20151120195625.GA1124@salvia> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20151120195625.GA1124@salvia> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1634 Lines: 43 Hello, David, Pablo. On Fri, Nov 20, 2015 at 08:56:25PM +0100, Pablo Neira Ayuso wrote: > > Pablo, are you ok with me merging this into net-next directly or > > would you rather I take patches 1-6 into net-next and then you can > > merge and then add patch #7 on top? > > I'd suggest you get 1-6, then I'll pull this info my tree. Thanks David! Hmm.... 1-3 will be needed to address similar issues in a different controller, so putting them in a separate branch would work best. I created a branch which contains the 1-3 on top of v4.4-rc1. git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup.git for-4.5-ancestor-test If creating a different branch from net side is better, please let me know. > Regarding #7, I have a couple two concerns: > > 1) cgroup currently doesn't work the way users expect, ie. to perform any > reasonable firewalling. Since this relies on early demux, only a > limited number of sockets get access to the cgroup info. Right, it doesn't work well on INPUT side, so the big warning in the man page. > 2) We have traditionally rejected match2 and target2 extensions. I > guess you can accomodate the new cgroup code through the revision > iptables infrastructure, so we still use the cgroup match. I thought it would be confusing because the two are completely separate. Hmmm... okay, I'll merge it into xt_cgroup. Thanks. -- tejun -- 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/