Subject: Re: [PATCH net-next v2 1/2] net, sched: Make tc-related drop reason more flexible

From: [email-masked]
Date: Mon, 16 Oct 2023 20:10:25 +0000

Hello:

This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <[email-masked]>:

On Mon,  9 Oct 2023 11:26:54 +0200 you wrote:
> Currently, the kfree_skb_reason() in sch_handle_{ingress,egress}() can only
> express a basic SKB_DROP_REASON_TC_INGRESS or SKB_DROP_REASON_TC_EGRESS reason.
> 
> Victor kicked-off an initial proposal to make this more flexible by disambiguating
> verdict from return code by moving the verdict into struct tcf_result and
> letting tcf_classify() return a negative error. If hit, then two new drop
> reasons were added in the proposal, that is SKB_DROP_REASON_TC_INGRESS_ERROR
> as well as SKB_DROP_REASON_TC_EGRESS_ERROR. Further analysis of the actual
> error codes would have required to attach to tcf_classify via kprobe/kretprobe
> to more deeply debug skb and the returned error.
> 
> [...]

Here is the summary with links:
  - [net-next,v2,1/2] net, sched: Make tc-related drop reason more flexible
    https://git.kernel.org/netdev/net-next/c/54a59aed395c
  - [net-next,v2,2/2] net, sched: Add tcf_set_drop_reason for {__,}tcf_classify
    https://git.kernel.org/netdev/net-next/c/39d08b91646d

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