All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: David Lee <david.lee@trailofbits.com>
Cc: vinicius.gomes@intel.com, kuba@kernel.org, jhs@mojatatu.com,
	jiri@resnulli.us, davem@davemloft.net, edumazet@kernel.org,
	pabeni@redhat.com, horms@kernel.org, kylebot@openai.com,
	dominik.czarnota@trailofbits.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH net v2] net: sched: prevent scheduling deactivated qdiscs
Date: Wed, 28 Oct 2026 10:02:02 +0000	[thread overview]
Message-ID: <179318172275.622019.2392717179120363996.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261023194712.package1-20-v2-david.lee@trailofbits.com>

Hello:

This patch was applied to netdev/net.git (main)
by Dave Miller <davem@davem-thinkpadp1gen8.ibmlond.csb>:

On Fri, 23 Oct 2026 16:02:56 -0400 you wrote:
> From: Kyle Zeng <kylebot@openai.com>
> 
> TAPRIO can schedule a deactivated qdisc after some_qdisc_is_busy() has
> reported it idle.
> 
> Commit 47e8dbb6e763 ("net/sched: do not reset queues in graft operations")
> made graft deactivation skip queue reset, leaving TAPRIO's timer armed.
> 
> [...]

Here is the summary with links:
  - [net,v2] net: sched: prevent scheduling deactivated qdiscs
    https://git.kernel.org/netdev/net/c/d6f81fd6abe2

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-10-28 10:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-23 20:02 [PATCH net v2] net: sched: prevent scheduling deactivated qdiscs David Lee
2026-10-27 20:34 ` netdev-bot+sashiko
2026-10-28 10:02 ` patchwork-bot+netdevbpf [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=179318172275.622019.2392717179120363996.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=david.lee@trailofbits.com \
    --cc=dominik.czarnota@trailofbits.com \
    --cc=edumazet@kernel.org \
    --cc=horms@kernel.org \
    --cc=jhs@mojatatu.com \
    --cc=jiri@resnulli.us \
    --cc=kuba@kernel.org \
    --cc=kylebot@openai.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=stable@vger.kernel.org \
    --cc=vinicius.gomes@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.