In preparation for FORTIFY_SOURCE performing compile-time and run-time
field bounds checking for memset(), avoid intentionally writing across
neighboring fields.
Use memset_after() so memset() doesn't get confused about writing
beyond the destination member that is intended to be the starting point
of zeroing through the end of the struct.
Additionally fix the common helper, ieee80211_tx_info_clear_status(),
which was not clearing ack_signal, but the open-coded versions
did. Johannes Berg points out this bug was introduced by commit
|
||
---|---|---|
.. | ||
eeprom.c | ||
eeprom.h | ||
fwio.c | ||
Kconfig | ||
led.c | ||
lmac.h | ||
main.c | ||
Makefile | ||
p54.h | ||
p54pci.c | ||
p54pci.h | ||
p54spi_eeprom.h | ||
p54spi.c | ||
p54spi.h | ||
p54usb.c | ||
p54usb.h | ||
txrx.c |