diff options
| author | Donald Sharp <sharpd@nvidia.com> | 2021-11-29 15:51:45 -0500 |
|---|---|---|
| committer | Donald Sharp <sharpd@nvidia.com> | 2021-11-29 15:51:45 -0500 |
| commit | c3343a755fb01e3be9efadad75be719a5b7a3676 (patch) | |
| tree | bdcabaed4e245653640b0926eb24024172a81224 /zebra/zebra_router.h | |
| parent | 31ccdb903ffca482c1cca5b9222204848a6cdeb1 (diff) | |
zebra: Prevent thread usage of data after it being freed
On startup we create a thread timer event to do a rib sweep
of the system. On shutdown we never stopped this timer and
as such we have a situation where a thread event could be run
on shutdown after the data for it has been freed. Here is the
crash I am seeing:
(gdb) bt
(gdb)
Save the thread data in zebra_router and stop the thread so we don't
accidently do work on shutdown we don't mean to. In this case
it happened in our topotests with some severe system load.
Essentially we happened to kill the zebra daemon just as the
graceful_restart timer popped here.
Signed-off-by: Donald Sharp <sharpd@nvidia.com>
Diffstat (limited to 'zebra/zebra_router.h')
| -rw-r--r-- | zebra/zebra_router.h | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/zebra/zebra_router.h b/zebra/zebra_router.h index 408f9cbee5..dd788216c7 100644 --- a/zebra/zebra_router.h +++ b/zebra/zebra_router.h @@ -196,6 +196,7 @@ struct zebra_router { * Time for when we sweep the rib from old routes */ time_t startup_time; + struct thread *sweeper; /* * The hash of nexthop groups associated with this router |