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>] [day] [month] [year] [list]
Date:   Thu, 9 May 2019 15:58:24 -0500
From:   Robert McCabe <>
Subject: Question about setting custom STAB

Awhile ago I submitted this iproute2 patch:

And the corresponding kernel patch:

To allow the setting of arbitrary qdisc size table so that the packet
scheduler code in __qdisc_calculate_pkt_len charges the correct
bandwidth per my custom link layer.  These patches were not applied
because the reviewers didn't like that I added another enumeration to

My question is: why is the setting of the STAB not exposed to
userspace applications?  This seems to be a powerful feature that is
more generic than hard-coding the STABs for TC_LINKLAYER_ETHERNET and
TC_LINK_LAYER_ATM.  Or maybe I'm missing something and there is
mechanism to do this without my iproute2 patch?

Powered by blists - more mailing lists