Hi Jon,
See my inline comment.
Regards,
Hoang
-Original Message-
From: Jon Maloy
Sent: Thursday, June 4, 2020 8:42 PM
To: Hoang Huu Le ; ma...@donjonn.com;
ying@windriver.com; tipc-discussion@lists.sourceforge.net
Subject: Re: [net-next] tipc: update a binding service via
From: Jon Maloy
Sent: Thursday, June 4, 2020 8:59 PM
To: Hoang Huu Le ;
tipc-discussion@lists.sourceforge.net; tipc-dek ;
Tuong Tong Lien ; Xin Long ;
Tung Quang Nguyen ; Ying Xue
Subject: Re: FW: [PATCH 2/2] tipc: update a binding service via broadcast
On 6/4/20 5:14 AM, Hoang Huu Le
From: Tuong Lien
Date: Wed, 3 Jun 2020 12:06:01 +0700
> syzbot found the following crash:
...
> Call Trace:
> tipc_sendstream+0x4c/0x70 net/tipc/socket.c:1533
> sock_sendmsg_nosec net/socket.c:652 [inline]
> sock_sendmsg+0xcf/0x120 net/socket.c:672
> sys_sendmsg+0x32f/0x810
On 6/4/20 5:14 AM, Hoang Huu Le wrote:
Hi Jon,
Please see my inline comment
Regards,
Hoang
*From:* Jon Maloy
*Sent:* Friday, May 29, 2020 11:11 PM
*To:* tipc-discussion@lists.sourceforge.net; tipc-dek
; Tuong Tong Lien
; Xin Long ; Tung
Quang Nguyen ; Ying Xue
*Subject:* Fwd: Re:
On 6/4/20 5:21 AM, Hoang Huu Le wrote:
Currently, updating binding table (add service binding to
name table/withdraw a service binding) is being sent over replicast.
However, if we are scaling up clusters to > 100 nodes/containers this
method is less affection because of looping through nodes
Currently, updating binding table (add service binding to
name table/withdraw a service binding) is being sent over replicast.
However, if we are scaling up clusters to > 100 nodes/containers this
method is less affection because of looping through nodes in a cluster one
by one.
It is worth to
Hi Jon,
Please see my inline comment
Regards,
Hoang
From: Jon Maloy
Sent: Friday, May 29, 2020 11:11 PM
To: tipc-discussion@lists.sourceforge.net; tipc-dek ;
Tuong Tong Lien ; Xin Long ;
Tung Quang Nguyen ; Ying Xue
Subject: Fwd: Re: FW: [PATCH 2/2] tipc: update a binding service via
