netdev - Re: [PATCH net-next 1/1] tipc: fix bug in broadcast synch message create function

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]

Message-Id: <20150729.164832.705060026020098916.davem@davemloft.net>
Date:	Wed, 29 Jul 2015 16:48:32 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	jon.maloy@...csson.com
Cc:	netdev@...r.kernel.org, paul.gortmaker@...driver.com,
	erik.hugne@...csson.com, ying.xue@...driver.com, maloy@...jonn.com,
	tipc-discussion@...ts.sourceforge.net
Subject: Re: [PATCH net-next 1/1] tipc: fix bug in broadcast synch message
 create function

From: Jon Maloy <jon.maloy@...csson.com>
Date: Wed, 29 Jul 2015 18:28:01 -0400

> In commit d999297c3dbbe7fdd832f7fa4ec84301e170b3e6
> ("tipc: reduce locking scope during packet reception") we introduced
> a new function tipc_build_bcast_sync_msg(), which carries initial
> synchronization data between two nodes at first contact and at
> re-contact. In this function, we missed to add synchronization data,
> with the effect that the broadcast link endpoints will fail to
> synchronize correctly at re-contact between a running and a restarted
> node. All other cases work as intended.
> 
> With this commit, we fix this bug.
> 
> Signed-off-by: Jon Maloy <jon.maloy@...csson.com>

Applied, thanks Jon.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html