Netdev List
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Jamal Hadi Salim <jhs@mojatatu.com>
Cc: Victor Nogueira <victor@mojatatu.com>,
	davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
	jiri@resnulli.us, horms@kernel.org, vega@nebusec.ai,
	netdev@vger.kernel.org, Yuan Tan <yuantan098@gmail.com>
Subject: Re: [PATCH net] net/sched: Avoid quadratic handle scan in qdisc_alloc_handle
Date: Wed, 16 Sep 2026 17:04:25 -0700	[thread overview]
Message-ID: <20260916170425.1c7a7cbe@kernel.org> (raw)
In-Reply-To: <CAM0EoMmiw_kVnK4RjTT_dkquw0YLSB5VgO_7EoV2WT_pQXbCYw@mail.gmail.com>

On Wed, 16 Sep 2026 06:34:57 -0400 Jamal Hadi Salim wrote:
> > IMO any attack from containers / user ns is hardening. If it leads
> > to a crash we take it via net _because it's a crash_ not because
> > user ns can trigger it.
> >  
> 
> Ok - will review the pending ones with this in mind.
> 
> FWIW, here are the rules we have been using:
> 
> It is net if: Regression (worked before, broke) or always-triggerable
> crash/UAF/leak/lockup
> This specific bug could potentially cause a soft lockup but it wasnt
> consistently...
> 
> It goes to net-next if:
> a) Never worked (adds a cap, validation, accounting, or enforcement
> that never existed, e.g. memcg-class)
> b) Doc/comment
> c) tests - although the exception we currently make is if we create a
> tdc test for a net patch then it goes to net just dont cc stable on
> it.
> 
> > > Since we have a few similar "grey" issues in our pending queue - so
> > > where's the line for net/net-next?  
>  [...]  
> 
> 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?

> The priority is capped at 9. So a priority 9 with net gets immediate attention.
> A priority 9 that requires root permission is not as important as
> priority 9 that requires cap_net_admin (-urn)
> Yuan has a taxonomy as well; he calls these L1 and L2 when we pull the
> reports from his system.
> There is an exception: Priority 10. These are assigned to bugs which
> require no root/cap_net_admin and other UPEs
> 
> We also capture all "pre-existing bugs" and address them when the
> pending queue is empty. Most of these end up being a waste after fixes
> go in.


  reply	other threads:[~2026-09-17  0:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-11 13:31 [PATCH net] net/sched: Avoid quadratic handle scan in qdisc_alloc_handle Victor Nogueira
2026-09-14  8:22 ` Simon Horman
2026-09-15  2:11 ` Jakub Kicinski
2026-09-15 11:50   ` Jamal Hadi Salim
2026-09-15 12:28     ` Eric Dumazet
2026-09-15 14:01       ` Jamal Hadi Salim
2026-09-15 15:53     ` Jakub Kicinski
2026-09-16 10:34       ` Jamal Hadi Salim
2026-09-17  0:04         ` Jakub Kicinski [this message]
2026-09-17 11:24           ` Jamal Hadi Salim
2026-09-18  0:46             ` Jakub Kicinski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20260916170425.1c7a7cbe@kernel.org \
    --to=kuba@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=jhs@mojatatu.com \
    --cc=jiri@resnulli.us \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=vega@nebusec.ai \
    --cc=victor@mojatatu.com \
    --cc=yuantan098@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox