Page MenuHomeFreeBSD

net80211: make sure calls to (*iv_update_bss)() are locked
ClosedPublic

Authored by bz on Jan 19 2024, 5:07 PM.
Tags
None
Referenced Files
Unknown Object (File)
Tue, Apr 9, 5:39 AM
Unknown Object (File)
Mar 2 2024, 4:43 PM
Unknown Object (File)
Feb 26 2024, 7:37 PM
Unknown Object (File)
Feb 19 2024, 10:15 PM
Unknown Object (File)
Feb 3 2024, 1:56 PM
Unknown Object (File)
Jan 28 2024, 7:34 PM
Unknown Object (File)
Jan 26 2024, 7:20 PM
Unknown Object (File)
Jan 22 2024, 9:28 PM

Details

Summary

It turned out thare various calls into (*iv_update_bss)(), that is
direct changes to vap->iv_bss in the old days, happened without
synchronisation.

Use locking assertions to document the requirement or status quo
at some callers given ic locking will eventually have to be dealt
with.

MFC after: 3 days

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

bz requested review of this revision.Jan 19 2024, 5:07 PM
This revision is now accepted and ready to land.Jan 23 2024, 5:22 PM

By the way, I forgot to ask, is it also helpful to add IEEE80211_LOCK_ASSERT in lkpi_iv_update_bss()?