qcacmn: Extend tid_lock in rx defrag store fragment path
Currently, we are Flushing fragments for peer as part of rx defrag clean up. There is the possibility that frag flush is called while we are accessing frags in rx defrag store fragment path in parallel. Which will cause access after the free issue. Extending lock in rx defrag store fragment path to avoid any parallel flush while accessing the frags. Change-Id: I1e897b195f61d80ea6738e9a93f7bcaaa04adc97 CRs-Fixed: 3065414
Loading
Please register or sign in to comment