From: Cong Wang <xiyou.wangcong@gmail.com>
To: netdev@vger.kernel.org
Cc: jiri@resnulli.us, jhs@mojatatu.com, willsroot@protonmail.com,
savy@syst3mfailure.io, Cong Wang <xiyou.wangcong@gmail.com>
Subject: [Patch net 0/2] net_sched: Fix gso_skb flushing during qdisc change
Date: Mon, 5 May 2025 17:15:47 -0700 [thread overview]
Message-ID: <20250506001549.65391-1-xiyou.wangcong@gmail.com> (raw)
This patchset contains a bug fix and its test cases, please check each
patch description for more details. To keep the bug fix minimum, I
intentionally limit the code changes to the cases reported here.
---
Cong Wang (2):
net_sched: Flush gso_skb list too during ->change()
selftests/tc-testing: Add qdisc limit trimming tests
include/net/sch_generic.h | 14 +++++++++++
net/sched/sch_codel.c | 2 +-
net/sched/sch_fq.c | 2 +-
net/sched/sch_fq_codel.c | 2 +-
net/sched/sch_fq_pie.c | 2 +-
net/sched/sch_hhf.c | 2 +-
net/sched/sch_pie.c | 2 +-
.../tc-testing/tc-tests/qdiscs/codel.json | 24 +++++++++++++++++++
.../tc-testing/tc-tests/qdiscs/fq.json | 22 +++++++++++++++++
.../tc-testing/tc-tests/qdiscs/fq_codel.json | 22 +++++++++++++++++
.../tc-testing/tc-tests/qdiscs/fq_pie.json | 22 +++++++++++++++++
.../tc-testing/tc-tests/qdiscs/hhf.json | 22 +++++++++++++++++
.../tc-testing/tc-tests/qdiscs/pie.json | 24 +++++++++++++++++++
13 files changed, 156 insertions(+), 6 deletions(-)
create mode 100644 tools/testing/selftests/tc-testing/tc-tests/qdiscs/pie.json
--
2.34.1
next reply other threads:[~2025-05-06 0:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-06 0:15 Cong Wang [this message]
2025-05-06 0:15 ` [Patch net 1/2] net_sched: Flush gso_skb list too during ->change() Cong Wang
2025-05-06 14:00 ` Savy
2025-05-06 20:40 ` Cong Wang
2025-05-06 0:15 ` [Patch net 2/2] selftests/tc-testing: Add qdisc limit trimming tests Cong Wang
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=20250506001549.65391-1-xiyou.wangcong@gmail.com \
--to=xiyou.wangcong@gmail.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=savy@syst3mfailure.io \
--cc=willsroot@protonmail.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