Fixed vlib_buffer_clone with stale chained buffers 85/12785/2
authorYoann Desmouceaux <ydesmouc@cisco.com>
Tue, 29 May 2018 11:38:44 +0000 (13:38 +0200)
committerDamjan Marion <dmarion.lists@gmail.com>
Tue, 29 May 2018 15:37:28 +0000 (15:37 +0000)
commit1977a3488e91c6a4074a5538730418031515b299
treea60752451a03ea4efaaa7ee33847dc98f09edc80
parent0a77040fa0f588f3c2d539aa1d3c500731520676
Fixed vlib_buffer_clone with stale chained buffers

When calling vlib_buffer_clone() on a source vlib_buffer with no next
buffer but whose total_length_not_including_first_buffer hadn't been
properly zeroed out, the total_length_not_including_first_buffer of
the clone was set to a wrong value.

(see https://lists.fd.io/g/vpp-dev/topic/19869395)

Change-Id: I4b503ece804e3933bb259be4c2148f84dafbea3e
Signed-off-by: Yoann Desmouceaux <ydesmouc@cisco.com>
src/vlib/buffer_funcs.h