Add temporary NOTIFY logs for customer side debugging in qos branch

Review Request #695 — Created March 5, 2025 and submitted

mmiriam
APV10
rel_apv_10_7_2_14_qos
AE-1230
pradeep, prajesh

AE-1230 Add temporary NOTIFY logs for customer side debugging (IP header, TCP header, Ether header)



Description From Last Updated

According to the documentation and general best practices for POSIX threads, you should not call pthread_mutex_init multiple times on a …

prajeshprajesh

should it be called only once?

prajeshprajesh

should we log it only for HASH_INSERT case?

prajeshprajesh
prajesh
  1. 
      
  2. should it be called only once?

    1. Fixed it by adding calling it in rirt_init()

  3. should we log it only for HASH_INSERT case?

    1. As discussed offline we may miss logs when case is HASH_NOINSERT and still got the entry in rts table

  4. 
      
prajesh
  1. 
      
  2. 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.

  3. 
      
mmiriam
prajesh
  1. Ship It!
  2. 
      
pradeep
  1. Ship It!
  2. 
      
mmiriam
Review request changed

Status: Closed (submitted)

Loading...