All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Kuniyuki Iwashima <kuniyu@google.com>
Cc: jhs@mojatatu.com, jiri@resnulli.us, davem@davemloft.net,
	edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
	horms@kernel.org, gustavo@embeddedor.com, kuni1840@gmail.com,
	netdev@vger.kernel.org, tarasmadan@google.com
Subject: Re: [PATCH v1 net] net/sched: cls_api: Don't replay RTM_GETCHAIN in tc_ctl_chain().
Date: Thu, 10 Sep 2026 10:10:06 +0000	[thread overview]
Message-ID: <178903500614.1334538.13024696735558909937.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260908205537.863484-1-kuniyu@google.com>

Hello:

This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:

On Tue,  8 Sep 2026 20:55:25 +0000 you wrote:
> If a netlink socket sends RTM_GETCHAIN requests repeatedly
> without recv()ing the responses, tc_ctl_chain() hogs CPU and
> triggers Hung Task splat. [0]
> 
> As caught in the stack trace, netlink_attachskb() could confuse
> tc_ctl_chain() by returning -EAGAIN when the userspace netlink
> socket's receive buffer is full.
> 
> [...]

Here is the summary with links:
  - [v1,net] net/sched: cls_api: Don't replay RTM_GETCHAIN in tc_ctl_chain().
    https://git.kernel.org/netdev/net/c/dff39930ad5e

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-10 10:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-08 20:55 [PATCH v1 net] net/sched: cls_api: Don't replay RTM_GETCHAIN in tc_ctl_chain() Kuniyuki Iwashima
2026-09-09 10:01 ` Jamal Hadi Salim
2026-09-09 16:46   ` Kuniyuki Iwashima
2026-09-09 22:03     ` Jamal Hadi Salim
2026-09-10 10:10 ` 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=178903500614.1334538.13024696735558909937.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=gustavo@embeddedor.com \
    --cc=horms@kernel.org \
    --cc=jhs@mojatatu.com \
    --cc=jiri@resnulli.us \
    --cc=kuba@kernel.org \
    --cc=kuni1840@gmail.com \
    --cc=kuniyu@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=tarasmadan@google.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.