Code Review / vpp.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(parent: f934202) | patch
VPP-1029: Don't call clib_longjmp(...) directly from the SIGTERM handler 14/8814/2
authorDave Barach <dave@barachs.net>
Fri, 13 Oct 2017 23:16:56 +0000 (19:16 -0400)
committerDamjan Marion <dmarion.lists@gmail.com>
Sat, 14 Oct 2017 09:08:41 +0000 (09:08 +0000)
commit903651caf320dfdaabd20a0e6f3cd0ffc843e02f
tree2a747a9ea4398e73d5695989f4b0c807b4ff93a8tree | snapshot
parentf9342023c19887da656133e2688a90d70383b0c5commit | diff
VPP-1029: Don't call clib_longjmp(...) directly from the SIGTERM handler

It's way too easy to imagine leaving a mutex or a spin-lock held in
the /vpe-api shared-memory segment, or elsewhere. Set a volatile
variable and check it in a safe place...

Change-Id: I9d91c38cffeb921143c272162d055c9c24a6c312
Signed-off-by: Dave Barach <dave@barachs.net>
src/vlib/main.h diff | blob | history
src/vlib/unix/main.c diff | blob | history
Vector Packet Processing