Fix longstanding next-frame clone bug 67/567/2
authorDave Barach <dave@barachs.net>
Fri, 18 Mar 2016 13:48:16 +0000 (09:48 -0400)
committerGerrit Code Review <gerrit@fd.io>
Fri, 18 Mar 2016 14:53:07 +0000 (14:53 +0000)
commitba8c540c52fc83237dff2eb87c259037da448e39
tree4a1e52d4343545fce6a0d2a7aa5dab3c6eaadd44
parentcb656303dfae0497c06ac925a08bda9f2b9d4d91
Fix longstanding next-frame clone bug

Do not propagate flags into cloned vlib_next_frame_t's.
vlib_next_frame_init(...) sets nf->frame_index to ~0. If it turns out
that the original flags include VLIB_FRAME_IS_ALLOCATED, the wheels
fall off. And so on.

Change-Id: I8de18653acfcc8eb20cee36f4eb5b9e82234f21b
Signed-off-by: Dave Barach <dave@barachs.net>
vlib/vlib/threads.c