summaryrefslogtreecommitdiff
path: root/include/net/red.h
diff options
context:
space:
mode:
authorJohannes Berg <johannes.berg@intel.com>2016-12-01 16:25:30 +0100
committerLuca Coelho <luciano.coelho@intel.com>2017-02-03 16:26:43 +0200
commit6ea29ce5749687d125d56b6748fa68eee1791f6e (patch)
tree9006af6866db0d05b1d64a2f1aa3640646e0d237 /include/net/red.h
parentcba84570a0eb8826bcd69627fd975935bdcf7eaf (diff)
iwlwifi: mvm: set AID to firmware only for associated stations
The firmware will soon actually look at the AID field, and when it does that it'll try to ensure that the AID is never changing. Due to the way the station is added, it may start with an invalid AID before it's associated, so to ensure a constant AID (once it becomes non-zero), track the station state and set the AID only when the station is associated and when it disassociates. Signed-off-by: Johannes Berg <johannes.berg@intel.com> Signed-off-by: Luca Coelho <luciano.coelho@intel.com>
Diffstat (limited to 'include/net/red.h')
0 files changed, 0 insertions, 0 deletions
sult in a SIGBUS being sent to the user process. The MEM errors form userspace will result in a SIGKILL and also cause the offending pages to be claimed so they are no longer used in future tasks. SIGKILL is used to ensure that the process does not try to coredump and result in an attempt to read the memory again from within kernel space. Although there is a HV call to scrub the memory (mem_scrub), there is no easy way to guarantee that the real memory address(es) are not used by other tasks. Clearing the error with mem_scrub would zero the memory and cause the other processes to proceed with bad data. The handling of other non-resumable errors remain unchanged and will cause a panic. ==================== Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/ieee802154/6lowpan/Makefile')