From: Tung Quang Nguyen <tung.quang.nguyen@est.tech>
To: Henry Martin <bsdhenrymartin@gmail.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"tipc-discussion@lists.sourceforge.net"
<tipc-discussion@lists.sourceforge.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
Jon Maloy <jmaloy@redhat.com>,
"David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Eric Dumazet <edumazet@kernel.org>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>
Subject: Re: [PATCH net v2] tipc: fix broadcast sender hang on last acker departure
Date: Wed, 14 Oct 2026 13:37:20 +0000 [thread overview]
Message-ID: <AM7P189MB1137302A763554D726AB1482C69D2@AM7P189MB1137.EURP189.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <20261012153357.1863316-1-bsdhenrymartin@gmail.com>
> @@ -406,6 +410,8 @@ void tipc_group_update_bc_members(struct tipc_group *grp, int len, bool ack)
> m->bc_acked = prev;
> ackers++;
> }
> + if (ack)
> + m->bc_pending = tipc_group_is_receiver(m);
> }
This needs to be done in a simple way:
@ -405,6 +405,7 @@ void tipc_group_update_bc_members(struct tipc_group *grp, int len, bool ack)
tipc_group_update_member(m, len);
m->bc_acked = prev;
ackers++;
+ m->bc_pending = ack;
}
}
prev parent reply other threads:[~2026-10-14 13:37 UTC|newest]
Thread overview: 9+ 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-14 13:37 ` Tung Quang Nguyen [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=AM7P189MB1137302A763554D726AB1482C69D2@AM7P189MB1137.EURP189.PROD.OUTLOOK.COM \
--to=tung.quang.nguyen@est.tech \
--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 \
/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®