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] [day] [month] [year] [list]
Date:	Tue, 14 Jan 2014 16:50:11 -0800
From: (Eric W. Biederman)
To:	Libo Chen <>
Cc:	Gao feng <>,
	Cong Wang <>,
	Simon Horman <>,
	Patrick McHardy <>,
	Linux Kernel Network Developers <>,, Serge Hallyn <>,, Eric Dumazet <>,,,
	David Miller <>,
	LKML <>,
Subject: Re: [RFC PATCH net-next 0/4] net_cls for sys container

Libo Chen <> writes:

> yes
> On 2014/1/6 16:42, Gao feng wrote:
>> 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.
> yes
>> 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
>> effect?
> both, the end result depends on a smaller.
>> In your patch, both qdisc rule are effective. it looks strange.
> qdisc is based nic, does not distinguish virtual or physics. if you are all set,
> it means that what you want.  so the logic is not the problemI and this appears to be normal.

My personal opinion on the matter is that the network class cgroup is
brain dead and should not be used.  It is impossible to use for
incomming packets, and it is part of the the problem plagued cgroup

You have real network interfaces to do your classification with you
don't need to enhance the network class cgroup.

The more this is asked about the more I think the network class cgroup
should be be taken out into the woods some dark night and left in a
shallow grave, never to bother us again.


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