From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: phx <phx0fer@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] net/sched: sch_cake: fix NAT destination port not being updated in cake_update_flowkeys
Date: Mon, 13 Apr 2026 12:07:34 +0200 [thread overview]
Message-ID: <87y0ircgwp.fsf@toke.dk> (raw)
In-Reply-To: <CAKvCo-yFnu3RBbiGkaVi-X5qX_hN1a-FYrBZfzB9UKz8k-PZtQ@mail.gmail.com>
phx <phx0fer@gmail.com> writes:
> You're right, "vulnerability" is too strong - it's a correctness
> bug, not a security issue. Thanks for picking it up.
Cool. Could you please re-send with an updated commit message? Thanks!
-Toke
pw-bot: cr
prev parent reply other threads:[~2026-04-13 10:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-13 8:47 [PATCH] net/sched: sch_cake: fix NAT destination port not being updated in cake_update_flowkeys Dudu Lu
2026-04-13 9:41 ` Toke Høiland-Jørgensen
[not found] ` <CAKvCo-yFnu3RBbiGkaVi-X5qX_hN1a-FYrBZfzB9UKz8k-PZtQ@mail.gmail.com>
2026-04-13 10:07 ` Toke Høiland-Jørgensen [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y0ircgwp.fsf@toke.dk \
--to=toke@toke.dk \
--cc=netdev@vger.kernel.org \
--cc=phx0fer@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