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

From: Jakub Kicinski <[email-masked]>
Date: Fri, 13 Oct 2023 14:17:22 -0700

On Mon,  9 Oct 2023 11:26:54 +0200 Daniel Borkmann 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.

I guess Jamal said "this week" so he has two more days? :) 
While we wait:

Reviewed-by: Jakub Kicinski <[email-masked]>