netdev - Re: [PATCH net-next] net/sched: store the last executed chain also for clsact egress

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:   Thu, 29 Jul 2021 21:20:05 +0000
From:   patchwork-bot+netdevbpf@...nel.org
To:     Davide Caratti <dcaratti@...hat.com>
Cc:     jhs@...atatu.com, xiyou.wangcong@...il.com, jiri@...nulli.us,
        netdev@...r.kernel.org, davem@...emloft.net, kuba@...nel.org,
        marcelo.leitner@...il.com, alaa@...dia.com
Subject: Re: [PATCH net-next] net/sched: store the last executed chain also for
 clsact egress

Hello:

This patch was applied to netdev/net-next.git (refs/heads/master):

On Wed, 28 Jul 2021 20:08:00 +0200 you wrote:
> currently, only 'ingress' and 'clsact ingress' qdiscs store the tc 'chain
> id' in the skb extension. However, userspace programs (like ovs) are able
> to setup egress rules, and datapath gets confused in case it doesn't find
> the 'chain id' for a packet that's "recirculated" by tc.
> Change tcf_classify() to have the same semantic as tcf_classify_ingress()
> so that a single function can be called in ingress / egress, using the tc
> ingress / egress block respectively.
> 
> [...]

Here is the summary with links:
  - [net-next] net/sched: store the last executed chain also for clsact egress
    https://git.kernel.org/netdev/net-next/c/3aa260559455

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html