ping: fix double-free crash under VMWare hypervisor 44/4844/2
authorAndrew Yourtchenko <ayourtch@gmail.com>
Tue, 24 Jan 2017 14:47:27 +0000 (15:47 +0100)
committerDave Wallace <dwallacelf@gmail.com>
Tue, 24 Jan 2017 16:57:57 +0000 (16:57 +0000)
commitf69ecfe09db52c672ccbe47e714bc9c9a70d5539
tree2f2ddc071bcd6e088751114719ea39b50f3b4e18
parent898171afd9c7d37bc223c6520edad54980ad12fb
ping: fix double-free crash under VMWare hypervisor

bi0 retrieval from the ping reply events vector was incorrectly done
always from the first element.

For TBD reason the sending of the ping requests under VMWare was batched,
as a result the replies arrive close enough to make the events arrive as
an array, which exposed this bug. KVM never exhibited this behavior, which
explains not seeing this issue there.

Change-Id: I485d6f983571e25baa9407c21ef604937586d8bd
Signed-off-by: Andrew Yourtchenko <ayourtch@gmail.com>
src/vnet/ip/ping.c