diff options
| author |   Steven <sluong@cisco.com> | 2017-02-24 10:03:22 -0800 |
|---|---|---|
| committer |   Damjan Marion <dmarion.lists@gmail.com> | 2017-03-17 12:57:53 +0000 |
| commit | 6aa75af2411a328caa23077778365ea8ba97dcc0 (patch) | |
| tree | eaaa83d0ef481a1a564ed796b75a46156c0f55bd /src/vlibmemory | |
| parent | b069a6910aa2b95316ccdb5d9e5b95143b9dc7c0 (diff) | |
vlib: fix potential crash in dispatch_node ELOG_DATA call
dispatch_node may be invoked from vlib main or worker threads. The call to
ELOG_DATA in dispatch_node passes the parameter &vm->elog_main. It works fine
when dispatch_node is invoked from the main thread. It does bad thing when it
is invoked from the worker thread.
While we are at it, make two additional enhancements to the same area.
1. Use ELOG_TRACK_DATA instead of ELOG_DATA to enhance g2 viewer presentation.
2. Since ELOG_DATA is in the data path, it could get very chatty. Make the call
to ELOG_TRACK_DATA conditional compile.
Change-Id: I80ca0eea10bc1e5d0d5549f9844dd9a34dbb65a2
Signed-off-by: Steven <sluong@cisco.com>
Diffstat (limited to 'src/vlibmemory')
0 files changed, 0 insertions, 0 deletions