lists.openwall.net   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  linux-cve-announce  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:   Wed, 5 Aug 2020 09:45:53 -0700
From:   Jakub Kicinski <kuba@...nel.org>
To:     satish dhote <sdhote926@...il.com>
Cc:     netdev@...r.kernel.org, xiyou.wangcong@...il.com, jiri@...nulli.us,
        jhs@...atatu.com, <daniel@...earbox.net>
Subject: Re: Question about TC filter

On Wed, 5 Aug 2020 11:08:08 +0530 satish dhote wrote:
> Hi Team,
> 
> I have a question regarding tc filter behavior. I tried to look
> for the answer over the web and netdev FAQ but didn't get the
> answer. Hence I'm looking for your help.
> 
> I added ingress qdisc for interface enp0s25 and then configured the
> tc filter as shown below, but after adding filters I realize that
> rule is reflected as a result of both ingress and egress filter
> command?  Is this the expected behaviour? or a bug? Why should the
> same filter be reflected in both ingress and egress path?
> 
> I understand that policy is always configured for ingress traffic,
> so I believe that filters should not be reflected with egress.
> Behaviour is same when I offloaded ovs flow to the tc software
> datapath.

I feel like this was discussed and perhaps fixed by:

a7df4870d79b ("net_sched: fix tcm_parent in tc filter dump")

What's your kernel version?

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ