-
-
branches/rel_apv_10_7_2_14_qos/usr/src/sys/click/netinet/click_eroute.c (Diff revision 1) should it be called only once?
-
branches/rel_apv_10_7_2_14_qos/usr/src/sys/click/netinet/click_eroute.c (Diff revision 1) should we log it only for HASH_INSERT case?
Add temporary NOTIFY logs for customer side debugging in qos branch
Review Request #695 — Created March 5, 2025 and submitted
| Information | |
|---|---|
| mmiriam | |
| APV10 | |
| rel_apv_10_7_2_14_qos | |
| AE-1230 | |
| Reviewers | |
| pradeep, prajesh | |
AE-1230 Add temporary NOTIFY logs for customer side debugging (IP header, TCP header, Ether header)
-
-
branches/rel_apv_10_7_2_14_qos/usr/src/sys/click/netinet/click_eroute.c (Diff revision 1) According to the documentation and general best practices for POSIX threads, you should not call pthread_mutex_init multiple times on a single mutex without first destroying it. Here's a breakdown:
Undefined Behavior:
Attempting to initialize an already initialized mutex results in undefined behavior. This means the program's outcome is unpredictable and could lead to errors, crashes, or unexpected results.
Error Conditions:
Implementations of the Pthreads library may detect attempts to re-initialize a mutex and return an EBUSY error. However, this behavior is not guaranteed, and the system might not always catch it.
