)]}' { "log": [ { "commit": "3aa8d5f9893c182eb27f0f6ab354a77edbf1b9f0", "tree": "b2cc0ac454542e114bf3fcb4d85c62d9074903f1", "parents": [ "3378d2099440cb3a14dc7531a3221d4140e186e2" ], "author": { "name": "ajs", "email": "ajs", "time": "Sat Dec 11 18:00:06 2004 +0000" }, "committer": { "name": "ajs", "email": "ajs", "time": "Sat Dec 11 18:00:06 2004 +0000" }, "message": "2004-12-11 Andrew J. Schorr \u003cajschorr@alumni.princeton.edu\u003e\n\n\t* ospf_packet.c: (ospf_db_desc) Should be static, not global.\n\t (ospf_hello,ospf_db_desc,ospf_ls_upd,ospf_ls_ack) Improve warning\n\t messages to include identifying information (e.g. router id).\n\t* ospf_nsm.c: (nsm_change_state) Improve info message to include\n\t router id and state names.\n" }, { "commit": "2a42e285ed1b3891a479e52bf0bab958d68ca18e", "tree": "7f58188e992943424474199f11849f04ce62c665", "parents": [ "e588f21f2adae26eaee8789bacc3a45002e86e94" ], "author": { "name": "ajs", "email": "ajs", "time": "Wed Dec 08 18:43:03 2004 +0000" }, "committer": { "name": "ajs", "email": "ajs", "time": "Wed Dec 08 18:43:03 2004 +0000" }, "message": "2004-12-08 Andrew J. Schorr \u003cajschorr@alumni.princeton.edu\u003e\n\n\t* *.c: Change level of debug messages to LOG_DEBUG.\n" }, { "commit": "eb1ce6059a00f3f0dd92c965aa5982907b54c00d", "tree": "ebd6583ba2f2f9909c25653d0349662e08c26ecf", "parents": [ "2e864cfa12724ec20e82f0a24e1be5929e3a0cef" ], "author": { "name": "hasso", "email": "hasso", "time": "Fri Oct 08 08:17:22 2004 +0000" }, "committer": { "name": "hasso", "email": "hasso", "time": "Fri Oct 08 08:17:22 2004 +0000" }, "message": "Compiler warnings fixes round 1.\n" }, { "commit": "beebba75167b33e05b5e02a41179ad0c13a0bcd7", "tree": "83b72a338e29f7f6cff2b83fd2c71e8615f9f8e5", "parents": [ "320ec10a24d8dd81d0aa011dc92e07877e4e02f8" ], "author": { "name": "hasso", "email": "hasso", "time": "Sun Jun 20 21:00:27 2004 +0000" }, "committer": { "name": "hasso", "email": "hasso", "time": "Sun Jun 20 21:00:27 2004 +0000" }, "message": "Remove ifdef\u0027s HAVE_NSSA. NSSA support is stable enough.\n" }, { "commit": "6898008484a562ff5bae178a6fb0bd885fe8b1e5", "tree": "27797ca6532ca0ef85f538ac8f3070639e579229", "parents": [ "1ef74ef70bdab672458c4d1e4cea24197066c0af" ], "author": { "name": "paul", "email": "paul", "time": "Tue Mar 25 05:07:42 2003 +0000" }, "committer": { "name": "paul", "email": "paul", "time": "Tue Mar 25 05:07:42 2003 +0000" }, "message": "2003-03-25 Paul Jakma \u003cpaul@dishone.st\u003e\n\n\t* sync to latest zebra CVS\n\t* spec file: updated and added define for ospf-api/client\n\nNB: OSPF-API has been broken by the zebra.org changes, which\nhas added struct ospf * as a new arg to many functions\n" }, { "commit": "09e4efdcb22ac13af3f6e3a38158871ed140e5e0", "tree": "5fa509af429208262d719c04a195f5cd58e49ffa", "parents": [ "2d59836a4fb16e2471560a47da7e5f75779c5807" ], "author": { "name": "paul", "email": "paul", "time": "Sat Jan 18 00:12:02 2003 +0000" }, "committer": { "name": "paul", "email": "paul", "time": "Sat Jan 18 00:12:02 2003 +0000" }, "message": "Date: Fri, 20 Dec 2002 17:28:45 +0900\nFrom: Masahiko Endo \u003cendo@suri.co.jp\u003e\nReply-To: zebra@zebra.org\nTo: zebra@zebra.org\nCc: kunihiro@zebra.org, yokota@kddlabs.co.jp\nSubject: [zebra 16823] [PATCH] Bugfix and new feature in Opaque-LSA\nhandling.\n\n----- * ----- * ----- * ----- * ----- * ----- * ----- * ----- * ----- * -----\nChanges 2002.12.20\n\n1. Bug fixes\n\n 1.1 When an opaque LSA is being removed from (or added to) the LSDB,\n it does not mean a change in network topology. Therefore, SPF\n recalculation should not be triggered in that case.\n There was an assertion failure problem \"assert (rn \u0026\u0026 rn-\u003einfo)\"\n inside the function \"ospf_ase_incremental_update()\", because\n the upper function \"ospf_lsa_maxage_walker_remover()\" called it\n when a type-11 opaque LSA is removed due to MaxAge.\n\n 1.2 Type-9 LSA is defined to have \"link-local\" flooding scope.\n In the Database exchange procedure with a new neighbor, a type-9\n LSA was added in the database summary of a DD message, even if\n the link is different from the one that have bound to.\n\n2. Feature enhancements\n\n 2.1 Though a \"wildcard\" concept to handle type-9/10/11 LSAs altogether\n has introduced about a year ago, it was only a symbol definition\n and actual handling mechanism was not implemented. Now it works.\n" }, { "commit": "2d59836a4fb16e2471560a47da7e5f75779c5807", "tree": "619901a67086c8eca741eee4e8b6b9810a3d86b9", "parents": [ "e04ab74d17b4f3456bd3eeefe2043584431b4ea2" ], "author": { "name": "paul", "email": "paul", "time": "Fri Jan 17 23:48:42 2003 +0000" }, "committer": { "name": "paul", "email": "paul", "time": "Fri Jan 17 23:48:42 2003 +0000" }, "message": "From endo@suri.co.jp Fri Jan 17 23:36:30 2003\nDate: Fri, 20 Dec 2002 17:58:43 +0900\nFrom: Masahiko Endo \u003cendo@suri.co.jp\u003e\nReply-To: zebra@zebra.org\nTo: zebra@zebra.org\nCc: kunihiro@zebra.org\nSubject: [zebra 16824] [PATCH] nsm_kill_neighbor\n\n [ The following text is in the \"ISO-2022-JP\" character set. ]\r\n [ Your display is set for the \"ISO-8859-1\" character set. ]\r\n [ Some characters may be displayed incorrectly. ]\n\nHi Ishiguro-san,\n\nHere is my problem analysis against the case that the ospfd crashes\nwhen an interface is brought down.\n\nWhen the ospfd receives a ZEBRA message \"ZEBRA_INTERFACE_DOWN\" from\nzebra daemon, the ospfd performs bunch of ospf-interface cleanup for\nthe notified zebra-interface.\nThere are cases that neighbor instance \"nbr\", which will be removed\nafterward, may scheduled in the NSM thread event queue. And when the\nNSM event thread is fired, dereference for this already freed \"nbr\"\npointer causes SIGSEGV.\nPlease take a look at following timeline of processing sequences.\n" } ] }