netdev - Re: [PATCH net-next] tipc: handle broadcast NAME

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Tue, 18 Dec 2018 21:51:09 -0800 (PST)
From:   David Miller <davem@...emloft.net>
To:     zhenbo.gao@...driver.com
Cc:     jon.maloy@...csson.com, tipc-discussion@...ts.sourceforge.net,
        netdev@...r.kernel.org, ying.xue@...driver.com,
        yue.tao@...driver.com
Subject: Re: [PATCH net-next] tipc: handle broadcast NAME_DISTRIBUTOR
 packet when receiving it

From: Zhenbo Gao <zhenbo.gao@...driver.com>
Date: Tue, 18 Dec 2018 17:43:52 +0800

> NAME_DISTRIBUTOR messages are transmitted through unicast link on TIPC
> 2.0, by contrast, the messages are delivered through broadcast link on
> TIPC 1.7. But at present, NAME_DISTRIBUTOR messages received by
> broadcast link cannot be handled in tipc_rcv() until an unicast message
> arrives, which may lead to a significant delay to update name table.
> 
> To avoid this delay, we will also deal with broadcast NAME_DISTRIBUTOR
> message on broadcast receive path.
> 
> Signed-off-by: Zhenbo Gao <zhenbo.gao@...driver.com>
> Reviewed-by: Ying Xue <ying.xue@...driver.com>

Applied, thank you.