45c8760063
Handle skb fraglist creation if parent skb has nr_frags. Currently it is being handled if parent skb has nr_frags associated with it and results into acessing invalid skb region. e.g: To understand example, consider below points: 1. Parent frag has 40 bytes of data(qdf_nbuf_data()) 2. Assume each frag is of size 10 bytes. ---------------------------------------------------------- |Parent_SKB -----> 1st Fraglist SKB - Cons SKB chained | ---------------------------------------------------------- | nbuf->Data : 40B | Nbuf->Data: 0B | ---------------------------------------------------------- | Nr Frags: 16 | Nr Frags: 10 | ---------------------------------------------------------- | Data Len: 160B (16 * 10) | Data Len: 100B (10 * 10) | ---------------------------------------------------------- | Nbuf->len: 200B ( 40 + 160) | Nbuf->len: 100B | ---------------------------------------------------------- While creating fraglist, Parent nbuf -> data_len will become 100 Bytes (Because of assignment '='). Logically it should be (160B + 100B). '+=' This change incorporate above handling. Change-Id: I9f63035aa44e6f85a803511cb19632178d3dc2e5
This is CNSS WLAN Host Driver for products starting from iHelium