When we exceed the limit of BSS entries, this function will free the
new entry, however, at this time, it is the last door to access the
inputed ies, so these ies will be unreferenced objects and cause memory
leak.
Therefore we should free its ies before deallocating the new entry, beside
of dropping it from hidden_list.
Signed-off-by: Nguyen Dinh Phi <redacted>
---
V2: - Add subsystem to the subject line.
- Use bss_ref_put function for better clean-up dynamically allocated
cfg80211_internal_bss objects. It helps to clean relative hidden_bss.
net/wireless/scan.c | 6 ++----
1 file changed, 2 insertions(+), 4 deletions(-)
On Mon, Jun 28, 2021 at 09:23:34PM +0800, Nguyen Dinh Phi wrote:
quoted hunk
When we exceed the limit of BSS entries, this function will free the
new entry, however, at this time, it is the last door to access the
inputed ies, so these ies will be unreferenced objects and cause memory
leak.
Therefore we should free its ies before deallocating the new entry, beside
of dropping it from hidden_list.
Signed-off-by: Nguyen Dinh Phi <redacted>
---
V2: - Add subsystem to the subject line.
- Use bss_ref_put function for better clean-up dynamically allocated
cfg80211_internal_bss objects. It helps to clean relative hidden_bss.
net/wireless/scan.c | 6 ++----
1 file changed, 2 insertions(+), 4 deletions(-)