All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Jamal Hadi Salim <jhs@mojatatu.com>
Cc: netdev@vger.kernel.org, jiri@resnulli.us, davem@davemloft.net,
	edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
	horms@kernel.org, victor@mojatatu.com, stable@vger.kernel.org,
	sashiko-bot@kernel.org, hybris@mojatatu.ai
Subject: Re: [PATCH net] net/sched: cls_api: reclaim an empty proto on the error path
Date: Sat, 26 Sep 2026 00:30:04 +0000	[thread overview]
Message-ID: <179038260440.3219877.10131915992681374207.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <QDISC-JCOT.v1.20260910090924@mojatatu.com>

Hello:

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

On Thu, 24 Sep 2026 04:32:49 -0400 you wrote:
> Two racing tc filter add requests on the same chain/prio of an
> unlocked classifier both run change() on the shared proto and both
> can fail: the winner's tcf_chain_tp_delete_empty() attempt gives up
> because the loser's handle is still in the idr, and the loser's
> error path drops only its own reference without a second reclamation
> attempt. The empty proto stays linked in the chain, holding the
> chain reference, a block reference and the classifier module
> reference until the chain or block is torn down.
> 
> [...]

Here is the summary with links:
  - [net] net/sched: cls_api: reclaim an empty proto on the error path
    https://git.kernel.org/netdev/net/c/0bb8eab29b55

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-26  0:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-24  8:32 [PATCH net] net/sched: cls_api: reclaim an empty proto on the error path Jamal Hadi Salim
2026-09-25 13:13 ` Simon Horman
2026-09-26  0:18 ` Jakub Kicinski
2026-09-26  9:49   ` Jamal Hadi Salim
2026-09-29  0:47     ` Jakub Kicinski
2026-09-29  8:42       ` Jamal Hadi Salim
2026-09-26  0:30 ` 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=179038260440.3219877.10131915992681374207.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=hybris@mojatatu.ai \
    --cc=jhs@mojatatu.com \
    --cc=jiri@resnulli.us \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sashiko-bot@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=victor@mojatatu.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.