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  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]
Date:	Mon, 06 Jan 2014 16:42:40 +0800
From:	Gao feng <>
To:	Libo Chen <>,
	Cong Wang <>
CC:	David Miller <>,
	Jamal Hadi Salim <>,
	Li Zefan <>,
	Eric Dumazet <>,,, Simon Horman <>,
	Serge Hallyn <>,
	Linux Kernel Network Developers <>,,,
	Patrick McHardy <>,,
	LKML <>
Subject: Re: [RFC PATCH net-next 0/4] net_cls for sys container

On 01/06/2014 03:54 PM, Libo Chen wrote:
> On 2014/1/3 13:20, Cong Wang wrote:
>> On Thu, Jan 2, 2014 at 7:11 PM, Libo Chen <> wrote:
>>> Hi guys,
>>> Now, lxc created with veth can not be under control by
>>> cls_cgroup.
>>> the former discussion:
>>> 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 what are you trying to achieve here?
> sys container using veth can be controlled by cls_cgroup basing on physic network interface

It's a problem about virtual nic, not container/net namespace.

If veth device is running in host. the skb is transmitted firstly by veth device and then delivered
by physical device. if you set both qdisc rule on veth and physical device. which qdisc rule will take

In your patch, both qdisc rule are effective. it looks strange.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists