All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Weiming Shi <bestswngs@gmail.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, horms@kernel.org, jhs@mojatatu.com,
	jiri@resnulli.us, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, dsahern@gmail.com, xmei5@asu.edu
Subject: Re: [PATCH net v2 0/1] net/sched: defer qdisc freeing after failed creation
Date: Sat, 05 Sep 2026 19:50:05 +0000	[thread overview]
Message-ID: <178863780539.1335621.17808621390639346249.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260902155231.2149915-1-bestswngs@gmail.com>

Hello:

This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Wed,  2 Sep 2026 23:52:30 +0800 you wrote:
> This is v2 of the qdisc failed-creation lifetime fix posted by Kyle Zeng
> and David Lee [1].  The public reproducer is available in a follow-up
> message [2].
> 
> When clsact binds a populated shared ingress block, ->init() can publish
> an embedded mini_Qdisc before qdisc_create() completes.  A later invalid
> TCA_RATE makes estimator setup fail.  The unwind removes the published
> pointer but frees the containing qdisc synchronously while tc_run() can
> still hold it.
> 
> [...]

Here is the summary with links:
  - [net,v2,1/1] net/sched: defer qdisc freeing after failed creation
    https://git.kernel.org/netdev/net/c/e6662f2100f8

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-09-05 19:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-02 15:52 [PATCH net v2 0/1] net/sched: defer qdisc freeing after failed creation Weiming Shi
2026-09-02 15:52 ` [PATCH net v2 1/1] " Weiming Shi
2026-09-05 19:50 ` 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=178863780539.1335621.17808621390639346249.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=bestswngs@gmail.com \
    --cc=davem@davemloft.net \
    --cc=dsahern@gmail.com \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=jhs@mojatatu.com \
    --cc=jiri@resnulli.us \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=xmei5@asu.edu \
    /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.