public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Libo Chen <clbchenlibo.chen@huawei.com>
To: David Miller <davem@davemloft.net>, <jhs@mojatatu.com>,
	Li Zefan <lizefan@huawei.com>
Cc: <edumazet@google.com>, <pshelar@nicira.com>,
	<jasowang@redhat.com>, <horms@verge.net.au>,
	Serge Hallyn <serge.hallyn@ubuntu.com>, <netdev@vger.kernel.org>,
	<cgroups@vger.kernel.org>,
	<containers@lists.linux-foundation.org>, <kaber@trash.net>,
	<xemul@openvz.org>, LKML <linux-kernel@vger.kernel.org>
Subject: [RFC PATCH net-next 0/4] net_cls for sys container
Date: Fri, 3 Jan 2014 11:11:00 +0800	[thread overview]
Message-ID: <52C62A44.4070304@huawei.com> (raw)

Hi guys,

Now, lxc created with veth can not be under control by
cls_cgroup.

the former discussion:
http://lkml.indiana.edu/hypermail/linux/kernel/1312.1/00214.html

In short, because cls_cgroup relys classid attached to sock
filter skb, but sock will be cleared inside dev_forward_skb()
in veth_xmit().

so I add backup_classid in struct sk_buffer to save classid
before dev_forward_skb(). In cls_cgroup_classify(), if skb->sk
is NULL, we can try to restore classid form skb->bk_classid.


Libo Chen (4):
  net: introduce bk_classid to struct sk_buff
  cls_cgroup: introduce a helper: bk_cls_classid()
  veth: backup classid befor switch net_ns
  cls_cgroup: restore classid from skb->sk_classid

 drivers/net/veth.c       |  5 +++++
 include/linux/skbuff.h   |  3 +++
 include/net/cls_cgroup.h | 11 +++++++++++
 net/sched/cls_cgroup.c   |  8 ++++----
 4 files changed, 23 insertions(+), 4 deletions(-)


             reply	other threads:[~2014-01-03  3:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-03  3:11 Libo Chen [this message]
2014-01-03  5:20 ` [RFC PATCH net-next 0/4] net_cls for sys container Cong Wang
2014-01-06  7:54   ` Libo Chen
2014-01-06  8:42     ` Gao feng
2014-01-06 10:06       ` Libo Chen
2014-01-15  0:50         ` Eric W. Biederman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=52C62A44.4070304@huawei.com \
    --to=clbchenlibo.chen@huawei.com \
    --cc=cgroups@vger.kernel.org \
    --cc=containers@lists.linux-foundation.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@verge.net.au \
    --cc=jasowang@redhat.com \
    --cc=jhs@mojatatu.com \
    --cc=kaber@trash.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizefan@huawei.com \
    --cc=netdev@vger.kernel.org \
    --cc=pshelar@nicira.com \
    --cc=serge.hallyn@ubuntu.com \
    --cc=xemul@openvz.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox