summaryrefslogtreecommitdiff
path: root/ospfd
AgeCommit message (Collapse)Author
2003-01-17From endo@suri.co.jp Fri Jan 17 23:36:30 2003paul
Date: Fri, 20 Dec 2002 17:58:43 +0900 From: Masahiko Endo <endo@suri.co.jp> Reply-To: zebra@zebra.org To: zebra@zebra.org Cc: kunihiro@zebra.org Subject: [zebra 16824] [PATCH] nsm_kill_neighbor [ The following text is in the "ISO-2022-JP" character set. ] [ Your display is set for the "ISO-8859-1" character set. ] [ Some characters may be displayed incorrectly. ] Hi Ishiguro-san, Here is my problem analysis against the case that the ospfd crashes when an interface is brought down. When the ospfd receives a ZEBRA message "ZEBRA_INTERFACE_DOWN" from zebra daemon, the ospfd performs bunch of ospf-interface cleanup for the notified zebra-interface. There are cases that neighbor instance "nbr", which will be removed afterward, may scheduled in the NSM thread event queue. And when the NSM event thread is fired, dereference for this already freed "nbr" pointer causes SIGSEGV. Please take a look at following timeline of processing sequences.
2002-12-13 Kevin C Miller <kevinm@andrew.cmu.edu>paul
[zebra 16681] OSPF NSSA Patches
2002-12-13[zebra 14631] Generic PtP and RFC3021 interface addressing supportpaul
2002-12-13zebra link state detection supportpaul
2002-12-13ospfd Point-to-Multipoint supportpaul
2002-12-13Greg Troxel <gdt@ir.bbn.com>paul
[zebra 15715] FIX for ospf md5 authentication problem, finally! fix copy of ospf packet buffer
2002-12-13zebra-ospfd-md5auth-seqnum.patch - paulj - change OSPF md5 sequence numberpaul
to be derived from time() to speed up synching after restart of ospfd
2002-12-13Initial revisionpaul