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: Mon, 16 Oct 2023 20:10:25 +0000
To: Daniel Borkmann <>
Subject: Re: [PATCH net-next v2 1/2] net,
 sched: Make tc-related drop reason more flexible


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

On Mon,  9 Oct 2023 11:26:54 +0200 you wrote:
> Currently, the kfree_skb_reason() in sch_handle_{ingress,egress}() can only
> 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
  - [net-next,v2,2/2] net, sched: Add tcf_set_drop_reason for {__,}tcf_classify

You are awesome, thank you!
Deet-doot-dot, I am a bot.

Powered by blists - more mailing lists