Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: Ren Wei <enjou1224z@gmail.com>,
	cake@lists.bufferbloat.net, netdev@vger.kernel.org,
	jhs@mojatatu.com, jiri@resnulli.us, davem@davemloft.net,
	edumazet@google.com, pabeni@redhat.com, horms@kernel.org,
	vega@nebusec.ai, zhilinz@nebusec.ai
Subject: [Cake] Re: [PATCH net 1/1] net/sched: sch_cake: validate 6in4 inner headers
Date: Tue, 28 Jul 2026 15:51:11 -0700	[thread overview]
Message-ID: <20260728155111.3463ac49@kernel.org> (raw)
In-Reply-To: <875x1zwfzz.fsf@toke.dk>

On Tue, 28 Jul 2026 12:44:16 +0200 Toke Høiland-Jørgensen wrote:
> > A malformed packet can therefore use an inner header with a non-IPv6
> > version while still setting the byte used as nexthdr to TCP. When two
> > packets from the same queued flow reach cake_ack_filter(), the version
> > dispatch can fall through to WARN_ON(1), which becomes a denial of
> > service on kernels with panic_on_warn enabled.  
> 
> Hmm, I seem to recall a policy that says we don't care about
> panic_on_warn-induced crashes? What say the maintainers?

Maybe in cases were it's triggered by root doing something stupid.
But packet triggered WARN will definitely cause eyebrows to shift
upwards.

> That being said, I am not sure an unconditional WARN_ON really serves
> any purpose here? As you've shown, this will most likely just be caused
> by malformed packets.
> 
> So rather than add all these new checks, how about we just get rid of
> the WARN_ON?

👍️

      reply	other threads:[~2026-07-28 22:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-27 17:03 [Cake] [PATCH net 0/1] net/sched: sch_cake: validate 6in4 inner headers Ren Wei
2026-07-27 17:03 ` [Cake] [PATCH net 1/1] " Ren Wei
2026-07-28 10:44   ` [Cake] " Toke Høiland-Jørgensen
2026-07-28 22:51     ` Jakub Kicinski [this message]

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

  List information: https://lists.bufferbloat.net/postorius/lists/cake.lists.bufferbloat.net/

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

  git send-email \
    --in-reply-to=20260728155111.3463ac49@kernel.org \
    --to=kuba@kernel.org \
    --cc=cake@lists.bufferbloat.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=enjou1224z@gmail.com \
    --cc=horms@kernel.org \
    --cc=jhs@mojatatu.com \
    --cc=jiri@resnulli.us \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=toke@toke.dk \
    --cc=vega@nebusec.ai \
    --cc=zhilinz@nebusec.ai \
    /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