mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Victor Nogueira <victor@mojatatu.com>
To: Ren Wei <enjou1224z@gmail.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-kselftest@vger.kernel.org
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, horms@kernel.org, jhs@mojatatu.com,
	jiri@resnulli.us, vega@nebusec.ai, milkory@outlook.com
Subject: Re: [PATCH net v2 2/2] selftests/tc-testing: add qdisc hierarchy depth tests
Date: Sat, 1 Aug 2026 13:35:39 -0300	[thread overview]
Message-ID: <8afa5643-12bd-4261-a148-7032d2ac87b5@mojatatu.com> (raw)
In-Reply-To: <5cc2d26a7c8e553759cdd29a3116f843fabc25ba.1785434373.git.milkory@outlook.com>

On 01/08/2026 10:42, Ren Wei wrote:
> From: Zijie Huang <milkory@outlook.com>
> 
> Add tdc coverage for the qdisc hierarchy depth limit.
> 
> The tests verify that the deepest allowed hierarchy can still be created
> and that adding another child qdisc below it is rejected.
> 
> Signed-off-by: Zijie Huang <milkory@outlook.com>
> Assisted-by: Codex:gpt-5.4
> Signed-off-by: Ren Wei <enjou1224z@gmail.com>

Reviewed-by: Victor Nogueira <victor@mojatatu.com>

  reply	other threads:[~2026-08-01 16:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-01 13:42 [PATCH net v2 0/2] net/sched: fix qdisc graft hierarchy validation Ren Wei
2026-08-01 13:42 ` [PATCH net v2 1/2] net/sched: reject overly deep qdisc hierarchies Ren Wei
2026-08-01 14:11   ` Jamal Hadi Salim
2026-08-01 14:30     ` Zijie Huang
2026-08-01 16:27   ` Victor Nogueira
2026-08-01 13:42 ` [PATCH net v2 2/2] selftests/tc-testing: add qdisc hierarchy depth tests Ren Wei
2026-08-01 16:35   ` Victor Nogueira [this message]
2026-08-01 14:13 ` [PATCH net v2 0/2] net/sched: fix qdisc graft hierarchy validation Jamal Hadi Salim
2026-08-06 13:40 ` patchwork-bot+netdevbpf

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=8afa5643-12bd-4261-a148-7032d2ac87b5@mojatatu.com \
    --to=victor@mojatatu.com \
    --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=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=milkory@outlook.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=vega@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

all inboxes | Powered by JetHome®