LinuxKPI: 802.11: lock down the "txq_scheduled" tailqHEADmain

For consistency rename the "scheduled_txqs" tailq to
"txq_scheduled" and add a lock per txq ("txq_scheduled_lock[]").
We use the "_bh" locking as this called from the device driver.

This fixes panics due to concurrent access to the tailq, especially
in between "first" and "remove" on the out-direction and between
"insert" and "elem_init" on the in-direction.

This was easily reproducible just running iperf3 at basic rates for
a few seconds to minutes with multiple chipsets, not only rtw89.

Sponsored by:	The FreeBSD Foundation
PR:		290636
Reported by:	arved, and others before
MFC after:	3 days

0 files changed, 0 insertions, 0 deletions