Thread (11 messages) flat view 11 messages, 5 authors, 9d ago

Re: [PATCH net] net/sched: Avoid quadratic handle scan in qdisc_alloc_handle

From: Jakub Kicinski <kuba@kernel.org>
Date: 2026-09-18 00:46:32

On Thu, 17 Sep 2026 07:24:05 -0400 Jamal Hadi Salim wrote:
On Wed, Sep 16, 2026 at 8:04 PM Jakub Kicinski [off-list ref] wrote:
quoted
quoted
Given the flood, here are the priority rules we are using:
1) submit net before net-next
2) All bugs must be reproducible by our (semi-automated) system
(hybris). I dont even look at issues unless they are reproducible
(hence my nagging "do you have a PoC?" ;->)
3) Assign a priority to each bug and submit the highest priority ones
first. The priorities are assigned as follows:
- base (reproduced, ACCURATE) +1
- Crash (oops/panic/NULL-deref/OOM/corruption) +2
- UAF +2
- Lockup (soft lockup/livelock/infinite loop) +1
- leak +1
- simple-trigger (plain tc/tdc, no special PoC) +1
- privilege required: (root) +1 / (unshare -Urn) +2
nice system :)
no distinction between control path-trigger an packet trigger?
At the moment we dont make a distinction - the existing point system
would still work, I think. Do you see it differently?
Right, a bit of a murky call. In abstract packet trigger could mean
remote attacker can crash a middlebox, that's _so_ much more serious.
But in practice most of our packet level attacks are for some insanely
pre-cooked skbs from AF_PACKET and such :/

It was just a thought. 
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help