mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Henry Martin <bsdhenrymartin@gmail.com>
Cc: jmaloy@redhat.com, tung.quang.nguyen@est.tech,
	davem@davemloft.net, kuba@kernel.org, edumazet@kernel.org,
	pabeni@redhat.com, horms@kernel.org, ying.xue@windriver.com,
	netdev@vger.kernel.org, tipc-discussion@lists.sourceforge.net,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH net v4] tipc: fix broadcast sender hang on last acker departure
Date: Thu, 22 Oct 2026 09:10:05 +0000	[thread overview]
Message-ID: <179266020503.1559266.4916570736972457348.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261019115859.3471295-1-bsdhenrymartin@gmail.com>

Hello:

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

On Mon, 19 Oct 2026 19:58:59 +0800 you wrote:
> TIPC group broadcast senders are blocked while a replicast still has
> outstanding member acks: tipc_group_bc_cong() returns true as long as
> grp->bc_ackers is non-zero, and clears *grp->open, which is what
> tipc_poll() uses to report EPOLLOUT (via tsk->group_is_open).
> 
> When the last outstanding acker departs before acking,
> tipc_group_delete_member() decrements grp->bc_ackers to zero but
> never restores *grp->open.  As a result poll(EPOLLOUT) never fires
> again.  A writer blocked in sendmsg() is only released if some other
> wakeup happens after the deletion: with TIPC_GROUP_MEMBER_EVTS the
> leave event delivery calls sk_data_ready() and wakes it, but without
> member events nothing does and it sleeps indefinitely, since the
> default send timeout is MAX_SCHEDULE_TIMEOUT.
> 
> [...]

Here is the summary with links:
  - [net,v4] tipc: fix broadcast sender hang on last acker departure
    https://git.kernel.org/netdev/net/c/f4377bf85887

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

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-09  5:56 [PATCH] tipc: fix broadcast sender hang and leak " Henry Martin
2026-10-09  6:00 ` netdev-bot+sinfo
2026-10-10  5:59 ` netdev-bot+sashiko
2026-10-12 11:45   ` Tung Quang Nguyen
2026-10-12 15:33     ` [PATCH net v2] tipc: fix broadcast sender hang " Henry Martin
2026-10-13 16:24       ` netdev-bot+sashiko
2026-10-14 13:40         ` Tung Quang Nguyen
2026-10-15  2:20           ` [PATCH net v3] " Henry Martin
2026-10-19 11:09             ` Tung Quang Nguyen
2026-10-19 11:58               ` [PATCH net v4] " Henry Martin
2026-10-22  1:11                 ` Tung Quang Nguyen
2026-10-22  9:10                 ` patchwork-bot+netdevbpf [this message]
2026-10-14 13:37       ` [PATCH net v2] " Tung Quang Nguyen

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=179266020503.1559266.4916570736972457348.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=bsdhenrymartin@gmail.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@kernel.org \
    --cc=horms@kernel.org \
    --cc=jmaloy@redhat.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=stable@vger.kernel.org \
    --cc=tipc-discussion@lists.sourceforge.net \
    --cc=tung.quang.nguyen@est.tech \
    --cc=ying.xue@windriver.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 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®