January 2023 - dev - lists.frrouting.org

FRR 8.4 Release
by Jafar Al-Gharaibeh 10 Aug '23

10 Aug '23

Dear FRR Community, We are pleased to announce FRR 8.4 release. Big thanks to all contributors. Packages are available at: Debian Packages - https://deb.frrouting.org RPM Packages - https://rpm.frrouting.org Snaps - https://snapcraft.io/frr Docker - frrouting/frr:v8.4.0 For release notes and a list of notable bug fixes, please visit: https://frrouting.org/release/8.4/ https://github.com/FRRouting/frr/releases/tag/frr-8.4 Cheers, The FRR Development Team!

1 3

Canceled: Weekly FRR YANG Meeting
by Pushpasis Sarkar 30 Jan '23

30 Jan '23

1 0

New Defects reported by Coverity Scan for freerangerouting/frr
by scan-admin＠coverity.com 25 Jan '23

25 Jan '23

Hi, Please find the latest report on new defect(s) introduced to freerangerouting/frr found with Coverity Scan. 4 new defect(s) introduced to freerangerouting/frr found with Coverity Scan. 9 defect(s), reported by Coverity Scan earlier, were marked fixed in the recent build analyzed by Coverity Scan. New defect(s) Reported-by: Coverity Scan Showing 4 of 4 defect(s) ** CID 1532182: (ATOMICITY) /zebra/zebra_dplane.c: 5555 in dplane_show_provs_helper() /zebra/zebra_dplane.c: 5555 in dplane_show_provs_helper() ________________________________________________________________________________________________________ *** CID 1532182: (ATOMICITY) /zebra/zebra_dplane.c: 5555 in dplane_show_provs_helper() 5549 5550 vty_out(vty, "%s (%u): in: %"PRIu64", q: %"PRIu64", q_max: %"PRIu64", out: %"PRIu64", q: %"PRIu64", q_max: %"PRIu64"\n", 5551 prov->dp_name, prov->dp_id, in, in_q, in_max, 5552 out, out_q, out_max); 5553 5554 DPLANE_LOCK(); >>> CID 1532182: (ATOMICITY) >>> Using an unreliable value of "prov" inside the second locked section. If the data that "prov" depends on was changed by another thread, this use might be incorrect. 5555 prov = dplane_prov_list_next(&zdplane_info.dg_providers, prov); 5556 DPLANE_UNLOCK(); 5557 } 5558 5559 return CMD_SUCCESS; 5560 } /zebra/zebra_dplane.c: 5555 in dplane_show_provs_helper() 5549 5550 vty_out(vty, "%s (%u): in: %"PRIu64", q: %"PRIu64", q_max: %"PRIu64", out: %"PRIu64", q: %"PRIu64", q_max: %"PRIu64"\n", 5551 prov->dp_name, prov->dp_id, in, in_q, in_max, 5552 out, out_q, out_max); 5553 5554 DPLANE_LOCK(); >>> CID 1532182: (ATOMICITY) >>> Using an unreliable value of "prov" inside the second locked section. If the data that "prov" depends on was changed by another thread, this use might be incorrect. 5555 prov = dplane_prov_list_next(&zdplane_info.dg_providers, prov); 5556 DPLANE_UNLOCK(); 5557 } 5558 5559 return CMD_SUCCESS; 5560 } ** CID 1532181: (ATOMICITY) /zebra/zebra_dplane.c: 6596 in dplane_work_pending() /zebra/zebra_dplane.c: 6596 in dplane_work_pending() ________________________________________________________________________________________________________ *** CID 1532181: (ATOMICITY) /zebra/zebra_dplane.c: 6596 in dplane_work_pending() 6590 dplane_provider_unlock(prov); 6591 6592 if (ctx != NULL) 6593 break; 6594 6595 DPLANE_LOCK(); >>> CID 1532181: (ATOMICITY) >>> Using an unreliable value of "prov" inside the second locked section. If the data that "prov" depends on was changed by another thread, this use might be incorrect. 6596 prov = dplane_prov_list_next(&zdplane_info.dg_providers, prov); 6597 DPLANE_UNLOCK(); 6598 } 6599 6600 if (ctx != NULL) 6601 ret = true; /zebra/zebra_dplane.c: 6596 in dplane_work_pending() 6590 dplane_provider_unlock(prov); 6591 6592 if (ctx != NULL) 6593 break; 6594 6595 DPLANE_LOCK(); >>> CID 1532181: (ATOMICITY) >>> Using an unreliable value of "prov" inside the second locked section. If the data that "prov" depends on was changed by another thread, this use might be incorrect. 6596 prov = dplane_prov_list_next(&zdplane_info.dg_providers, prov); 6597 DPLANE_UNLOCK(); 6598 } 6599 6600 if (ctx != NULL) 6601 ret = true; ** CID 1532180: (ATOMICITY) /zebra/zebra_dplane.c: 6972 in zebra_dplane_start() /zebra/zebra_dplane.c: 6972 in zebra_dplane_start() ________________________________________________________________________________________________________ *** CID 1532180: (ATOMICITY) /zebra/zebra_dplane.c: 6972 in zebra_dplane_start() 6966 6967 if (prov->dp_start) 6968 (prov->dp_start)(prov); 6969 6970 /* Locate next provider */ 6971 DPLANE_LOCK(); >>> CID 1532180: (ATOMICITY) >>> Using an unreliable value of "prov" inside the second locked section. If the data that "prov" depends on was changed by another thread, this use might be incorrect. 6972 prov = dplane_prov_list_next(&zdplane_info.dg_providers, prov); 6973 DPLANE_UNLOCK(); 6974 } 6975 6976 frr_pthread_run(zdplane_info.dg_pthread, NULL); 6977 } /zebra/zebra_dplane.c: 6972 in zebra_dplane_start() 6966 6967 if (prov->dp_start) 6968 (prov->dp_start)(prov); 6969 6970 /* Locate next provider */ 6971 DPLANE_LOCK(); >>> CID 1532180: (ATOMICITY) >>> Using an unreliable value of "prov" inside the second locked section. If the data that "prov" depends on was changed by another thread, this use might be incorrect. 6972 prov = dplane_prov_list_next(&zdplane_info.dg_providers, prov); 6973 DPLANE_UNLOCK(); 6974 } 6975 6976 frr_pthread_run(zdplane_info.dg_pthread, NULL); 6977 } ** CID 1532179: (ATOMICITY) /zebra/zebra_dplane.c: 6826 in dplane_thread_loop() /zebra/zebra_dplane.c: 6826 in dplane_thread_loop() ________________________________________________________________________________________________________ *** CID 1532179: (ATOMICITY) /zebra/zebra_dplane.c: 6826 in dplane_thread_loop() 6820 if (IS_ZEBRA_DEBUG_DPLANE_DETAIL) 6821 zlog_debug("dplane dequeues %d completed work from provider %s", 6822 counter, dplane_provider_get_name(prov)); 6823 6824 /* Locate next provider */ 6825 DPLANE_LOCK(); >>> CID 1532179: (ATOMICITY) >>> Using an unreliable value of "prov" inside the second locked section. If the data that "prov" depends on was changed by another thread, this use might be incorrect. 6826 prov = dplane_prov_list_next(&zdplane_info.dg_providers, prov); 6827 DPLANE_UNLOCK(); 6828 } 6829 6830 /* 6831 * We hit the work limit while processing at least one provider's /zebra/zebra_dplane.c: 6826 in dplane_thread_loop() 6820 if (IS_ZEBRA_DEBUG_DPLANE_DETAIL) 6821 zlog_debug("dplane dequeues %d completed work from provider %s", 6822 counter, dplane_provider_get_name(prov)); 6823 6824 /* Locate next provider */ 6825 DPLANE_LOCK(); >>> CID 1532179: (ATOMICITY) >>> Using an unreliable value of "prov" inside the second locked section. If the data that "prov" depends on was changed by another thread, this use might be incorrect. 6826 prov = dplane_prov_list_next(&zdplane_info.dg_providers, prov); 6827 DPLANE_UNLOCK(); 6828 } 6829 6830 /* 6831 * We hit the work limit while processing at least one provider's ________________________________________________________________________________________________________ To view the defects in Coverity Scan visit, https://u15810271.ct.sendgrid.net/ls/click?upn=HRESupC-2F2Czv4BOaCWWCy7my0P…

1 0

FRR 8.4.2 Bug Fix Release
by Jafar Al-Gharaibeh 14 Jan '23

14 Jan '23

Dear FRR Community, We are pleased to announce another bug fix release: FRR 8.4.2. Important Note: we have migrated away from Dockerhub to quay.io to host FRR docker images. Moving forward, all docker images will be found at: https://quay.io/repository/frrouting/frr Thank you all for your feedback. Packages are available at: Debian Packages - https://deb.frrouting.org RPM Packages - https://rpm.frrouting.org Snaps - https://snapcraft.io/frr Docker - https://quay.io/repository/frrouting/frr/manifest/sha256:54f9a7b9e5436430de… For release notes and a list of notable bug fixes, please visit: https://frrouting.org/release/8.4.2/ https://github.com/FRRouting/frr/releases/tag/frr-8.4.2 Cheers, The FRR Development Team!

1 0

frr using netconf datastores?
by Thomas.Swendseid＠gd-ms.com 06 Jan '23

06 Jan '23

Dear FRR Dev team, I had a question on whether the FRR in its current implementation works with Netconf and Yang? I do believe it does but I haven't been able to fully piece this together from the available documentation and other sources. I have downloaded the FRR (v 8.4.1), compiled it, and started it such that the ospfd is up and running. I've started netopeer2-server and netopeer2-cli and I can connect and see the datastores (running, candidate, startup) available. But my question is whether ospfd is consuming the 'startup' or 'running' datastore? The FRR was compiled with sysrepo enabled as well as specifying "-M sysrepo" on the ospfd command line. I'm not seeing any output from the daemon that would make me think it's using the datastore. Do I have to implement any callbacks or do any development work to have the ospfd use the datastore? Thanks for your help. Tom Swendseid [cid:image001.jpg@01D90EFC.D9804570] (480) 441.8173 thomas.swendseid(a)gd-ms.com<mailto:thomas.swendseid@gd-ms.com> This message and/or attachments may include information subject to GD Corporate Policies 07-103 and 07-105 and is intended to be accessed only by authorized recipients. Use, storage and transmission are governed by General Dynamics and its policies. Contractual restrictions apply to third parties. Recipients should refer to the policies or contract to determine proper handling. Unauthorized review, use, disclosure or distribution is prohibited. If you are not an intended recipient, please contact the sender and destroy all copies of the original message.

1 1