2019-06-04 10:11:33 +02:00
|
|
|
|
2007-07-27 15:43:23 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-09-03 15:24:57 +03:00
|
|
|
|
2017-04-26 12:14:59 +02:00
|
|
|
|
2026-01-30 16:21:07 +01:00
|
|
|
|
2007-07-27 15:43:23 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-07-15 11:47:34 -04:00
|
|
|
|
2007-07-27 15:43:23 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-11-18 16:54:50 +01:00
|
|
|
|
2007-09-17 11:56:21 -07:00
|
|
|
|
2007-07-27 15:43:23 +02:00
|
|
|
|
2007-11-09 01:57:29 +01:00
|
|
|
|
2023-08-27 14:05:21 +03:00
|
|
|
|
2007-07-27 15:43:23 +02:00
|
|
|
|
|
|
|
|
|
2009-04-23 18:52:52 +02:00
|
|
|
|
2008-04-08 15:14:40 -04:00
|
|
|
|
2008-02-23 15:17:11 +01:00
|
|
|
|
2007-07-27 15:43:23 +02:00
|
|
|
|
2009-04-14 10:09:24 +02:00
|
|
|
|
cfg80211: rework key operation
This reworks the key operation in cfg80211, and now only
allows, from userspace, configuring keys (via nl80211)
after the connection has been established (in managed
mode), the IBSS been joined (in IBSS mode), at any time
(in AP[_VLAN] modes) or never for all the other modes.
In order to do shared key authentication correctly, it
is now possible to give a WEP key to the AUTH command.
To configure static WEP keys, these are given to the
CONNECT or IBSS_JOIN command directly, for a userspace
SME it is assumed it will configure it properly after
the connection has been established.
Since mac80211 used to check the default key in IBSS
mode to see whether or not the network is protected,
it needs an update in that area, as well as an update
to make use of the WEP key passed to auth() for shared
key authentication.
Signed-off-by: Johannes Berg <johannes@sipsolutions.net>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
2009-07-08 14:22:54 +02:00
|
|
|
|
2007-07-27 15:43:23 +02:00
|
|
|
|
|
|
|
|
|
2014-01-20 23:55:44 +01:00
|
|
|
|
2007-07-27 15:43:23 +02:00
|
|
|
|
2009-01-22 15:05:53 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2007-07-27 15:43:23 +02:00
|
|
|
|
2024-01-29 19:34:36 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-09-21 19:28:14 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-06-12 00:19:45 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-09-21 19:28:14 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-02-25 16:27:43 +01:00
|
|
|
|
2007-07-27 15:43:23 +02:00
|
|
|
|
2011-11-16 15:28:55 +01:00
|
|
|
|
2009-03-23 17:28:35 +01:00
|
|
|
|
2007-07-27 15:43:23 +02:00
|
|
|
|
2011-11-16 15:28:55 +01:00
|
|
|
|
2009-03-23 17:28:35 +01:00
|
|
|
|
|
|
|
|
|
2011-11-16 15:28:55 +01:00
|
|
|
|
2007-07-27 15:43:23 +02:00
|
|
|
|
|
|
|
|
|
2016-04-12 15:56:15 +02:00
|
|
|
|
2023-08-29 12:17:44 +02:00
|
|
|
|
2007-07-27 15:43:23 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-04-12 15:56:15 +02:00
|
|
|
|
2007-07-27 15:43:23 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-07-08 16:55:51 +02:00
|
|
|
|
2007-07-27 15:43:23 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-07-08 16:55:51 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-07-08 16:55:53 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2007-07-27 15:43:23 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2007-12-19 01:31:26 +01:00
|
|
|
|
|
|
|
|
|
2016-04-12 15:56:15 +02:00
|
|
|
|
2008-01-24 19:38:38 +01:00
|
|
|
|
|
|
|
|
|
2007-07-27 15:43:23 +02:00
|
|
|
|
2008-09-12 22:52:47 +02:00
|
|
|
|
2007-07-27 15:43:23 +02:00
|
|
|
|
2023-08-29 12:17:44 +02:00
|
|
|
|
2008-09-12 22:52:47 +02:00
|
|
|
|
2007-07-27 15:43:23 +02:00
|
|
|
|
2008-01-24 19:38:38 +01:00
|
|
|
|
2008-09-12 22:52:47 +02:00
|
|
|
|
|
|
|
|
|
2008-10-11 01:51:51 +02:00
|
|
|
|
2022-07-12 10:49:23 +02:00
|
|
|
|
2008-09-12 22:52:47 +02:00
|
|
|
|
|
|
|
|
|
2008-01-24 19:38:38 +01:00
|
|
|
|
2012-04-11 08:47:56 +02:00
|
|
|
|
2023-08-29 12:17:44 +02:00
|
|
|
|
2007-07-27 15:43:23 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2007-12-19 01:31:26 +01:00
|
|
|
|
|
|
|
|
|
2008-05-15 12:55:29 +02:00
|
|
|
|
2007-07-27 15:43:23 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-09-12 22:52:47 +02:00
|
|
|
|
2007-12-28 14:32:58 +01:00
|
|
|
|
2023-08-29 12:17:44 +02:00
|
|
|
|
2007-07-27 15:43:23 +02:00
|
|
|
|
2008-05-15 12:55:27 +02:00
|
|
|
|
|
|
|
|
|
2012-04-11 08:47:56 +02:00
|
|
|
|
2007-07-27 15:43:23 +02:00
|
|
|
|
2008-09-12 22:52:47 +02:00
|
|
|
|
2007-07-27 15:43:24 +02:00
|
|
|
|
2008-05-15 12:55:29 +02:00
|
|
|
|
2008-01-24 19:38:38 +01:00
|
|
|
|
|
|
|
|
|
2008-09-12 22:52:47 +02:00
|
|
|
|
|
|
|
|
|
2008-10-11 01:51:51 +02:00
|
|
|
|
2022-07-12 10:49:23 +02:00
|
|
|
|
2008-09-12 22:52:47 +02:00
|
|
|
|
|
|
|
|
|
2007-07-27 15:43:23 +02:00
|
|
|
|
2023-08-29 12:17:44 +02:00
|
|
|
|
2013-07-08 16:55:53 +02:00
|
|
|
|
2007-07-27 15:43:23 +02:00
|
|
|
|
2013-07-08 16:55:53 +02:00
|
|
|
|
2023-08-29 12:17:44 +02:00
|
|
|
|
2007-07-27 15:43:23 +02:00
|
|
|
|
2013-07-08 16:55:53 +02:00
|
|
|
|
2023-08-29 12:17:44 +02:00
|
|
|
|
2007-07-27 15:43:23 +02:00
|
|
|
|
2013-07-08 16:55:53 +02:00
|
|
|
|
2023-08-29 12:17:44 +02:00
|
|
|
|
2007-07-27 15:43:23 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2007-12-19 01:31:26 +01:00
|
|
|
|
|
|
|
|
|
2007-07-27 15:43:23 +02:00
|
|
|
|
2008-05-15 12:55:29 +02:00
|
|
|
|
2007-07-27 15:43:23 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-09-12 22:52:47 +02:00
|
|
|
|
2007-12-28 14:32:58 +01:00
|
|
|
|
2023-08-29 12:17:44 +02:00
|
|
|
|
2007-07-27 15:43:23 +02:00
|
|
|
|
2008-05-15 12:55:27 +02:00
|
|
|
|
|
|
|
|
|
2012-04-11 08:47:56 +02:00
|
|
|
|
2007-07-27 15:43:23 +02:00
|
|
|
|
2008-09-12 22:52:47 +02:00
|
|
|
|
2007-07-27 15:43:24 +02:00
|
|
|
|
2008-05-15 12:55:29 +02:00
|
|
|
|
2008-01-24 19:38:38 +01:00
|
|
|
|
2008-09-12 22:52:47 +02:00
|
|
|
|
|
|
|
|
|
2008-10-11 01:51:51 +02:00
|
|
|
|
2022-07-12 10:49:23 +02:00
|
|
|
|
2008-09-12 22:52:47 +02:00
|
|
|
|
|
|
|
|
|
2007-07-27 15:43:23 +02:00
|
|
|
|
2023-08-29 12:17:44 +02:00
|
|
|
|
2013-07-08 16:55:53 +02:00
|
|
|
|
2007-07-27 15:43:23 +02:00
|
|
|
|
2013-07-08 16:55:53 +02:00
|
|
|
|
2023-08-29 12:17:44 +02:00
|
|
|
|
2008-05-15 12:55:29 +02:00
|
|
|
|
2007-07-27 15:43:23 +02:00
|
|
|
|
2013-07-08 16:55:53 +02:00
|
|
|
|
2023-08-29 12:17:44 +02:00
|
|
|
|
2007-07-27 15:43:23 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-10-09 18:30:38 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-03-14 22:11:22 +01:00
|
|
|
|
|
|
|
|
|
2022-10-09 18:30:38 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-03-14 22:11:22 +01:00
|
|
|
|
2022-10-09 18:30:38 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
mac80211: add stop/start logic for software TXQs
Sometimes, it is required to stop the transmissions momentarily and
resume it later; stopping the txqs becomes very critical in scenarios where
the packet transmission has to be ceased completely. For example, during
the hardware restart, during off channel operations,
when initiating CSA(upon detecting a radar on the DFS channel), etc.
The TX queue stop/start logic in mac80211 works well in stopping the TX
when drivers make use of netdev queues, i.e, when Qdiscs in network layer
take care of traffic scheduling. Since the devices implementing
wake_tx_queue can run without Qdiscs, packets will be handed to mac80211
directly without queueing them in the netdev queues.
Also, mac80211 does not invoke any of the
netif_stop_*/netif_wake_* APIs if wake_tx_queue is implemented.
Since the queues are not stopped in this case, transmissions can continue
and this will impact negatively on the operation of the wireless device.
For example,
During hardware restart, we stop the netdev queues so that packets are
not sent to the driver. Since ath10k implements wake_tx_queue,
TX queues will not be stopped and packets might reach the hardware while
it is restarting; this can make hardware unresponsive and the only
possible option for recovery is to reboot the entire system.
There is another problem to this, it is observed that the packets
were sent on the DFS channel for a prolonged duration after radar
detection impacting the channel closing time.
We can still invoke netif stop/wake APIs when wake_tx_queue is implemented
but this could lead to packet drops in network layer; adding stop/start
logic for software TXQs in mac80211 instead makes more sense; the change
proposed adds the same in mac80211.
Signed-off-by: Manikanta Pubbisetty <mpubbise@codeaurora.org>
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2018-07-11 00:12:53 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-03-26 12:14:31 +02:00
|
|
|
|
mac80211: add stop/start logic for software TXQs
Sometimes, it is required to stop the transmissions momentarily and
resume it later; stopping the txqs becomes very critical in scenarios where
the packet transmission has to be ceased completely. For example, during
the hardware restart, during off channel operations,
when initiating CSA(upon detecting a radar on the DFS channel), etc.
The TX queue stop/start logic in mac80211 works well in stopping the TX
when drivers make use of netdev queues, i.e, when Qdiscs in network layer
take care of traffic scheduling. Since the devices implementing
wake_tx_queue can run without Qdiscs, packets will be handed to mac80211
directly without queueing them in the netdev queues.
Also, mac80211 does not invoke any of the
netif_stop_*/netif_wake_* APIs if wake_tx_queue is implemented.
Since the queues are not stopped in this case, transmissions can continue
and this will impact negatively on the operation of the wireless device.
For example,
During hardware restart, we stop the netdev queues so that packets are
not sent to the driver. Since ath10k implements wake_tx_queue,
TX queues will not be stopped and packets might reach the hardware while
it is restarting; this can make hardware unresponsive and the only
possible option for recovery is to reboot the entire system.
There is another problem to this, it is observed that the packets
were sent on the DFS channel for a prolonged duration after radar
detection impacting the channel closing time.
We can still invoke netif stop/wake APIs when wake_tx_queue is implemented
but this could lead to packet drops in network layer; adding stop/start
logic for software TXQs in mac80211 instead makes more sense; the change
proposed adds the same in mac80211.
Signed-off-by: Manikanta Pubbisetty <mpubbise@codeaurora.org>
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2018-07-11 00:12:53 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-10-01 13:19:23 +02:00
|
|
|
|
|
|
|
|
|
mac80211: add stop/start logic for software TXQs
Sometimes, it is required to stop the transmissions momentarily and
resume it later; stopping the txqs becomes very critical in scenarios where
the packet transmission has to be ceased completely. For example, during
the hardware restart, during off channel operations,
when initiating CSA(upon detecting a radar on the DFS channel), etc.
The TX queue stop/start logic in mac80211 works well in stopping the TX
when drivers make use of netdev queues, i.e, when Qdiscs in network layer
take care of traffic scheduling. Since the devices implementing
wake_tx_queue can run without Qdiscs, packets will be handed to mac80211
directly without queueing them in the netdev queues.
Also, mac80211 does not invoke any of the
netif_stop_*/netif_wake_* APIs if wake_tx_queue is implemented.
Since the queues are not stopped in this case, transmissions can continue
and this will impact negatively on the operation of the wireless device.
For example,
During hardware restart, we stop the netdev queues so that packets are
not sent to the driver. Since ath10k implements wake_tx_queue,
TX queues will not be stopped and packets might reach the hardware while
it is restarting; this can make hardware unresponsive and the only
possible option for recovery is to reboot the entire system.
There is another problem to this, it is observed that the packets
were sent on the DFS channel for a prolonged duration after radar
detection impacting the channel closing time.
We can still invoke netif stop/wake APIs when wake_tx_queue is implemented
but this could lead to packet drops in network layer; adding stop/start
logic for software TXQs in mac80211 instead makes more sense; the change
proposed adds the same in mac80211.
Signed-off-by: Manikanta Pubbisetty <mpubbise@codeaurora.org>
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2018-07-11 00:12:53 +05:30
|
|
|
|
2022-05-31 21:08:24 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
mac80211: add stop/start logic for software TXQs
Sometimes, it is required to stop the transmissions momentarily and
resume it later; stopping the txqs becomes very critical in scenarios where
the packet transmission has to be ceased completely. For example, during
the hardware restart, during off channel operations,
when initiating CSA(upon detecting a radar on the DFS channel), etc.
The TX queue stop/start logic in mac80211 works well in stopping the TX
when drivers make use of netdev queues, i.e, when Qdiscs in network layer
take care of traffic scheduling. Since the devices implementing
wake_tx_queue can run without Qdiscs, packets will be handed to mac80211
directly without queueing them in the netdev queues.
Also, mac80211 does not invoke any of the
netif_stop_*/netif_wake_* APIs if wake_tx_queue is implemented.
Since the queues are not stopped in this case, transmissions can continue
and this will impact negatively on the operation of the wireless device.
For example,
During hardware restart, we stop the netdev queues so that packets are
not sent to the driver. Since ath10k implements wake_tx_queue,
TX queues will not be stopped and packets might reach the hardware while
it is restarting; this can make hardware unresponsive and the only
possible option for recovery is to reboot the entire system.
There is another problem to this, it is observed that the packets
were sent on the DFS channel for a prolonged duration after radar
detection impacting the channel closing time.
We can still invoke netif stop/wake APIs when wake_tx_queue is implemented
but this could lead to packet drops in network layer; adding stop/start
logic for software TXQs in mac80211 instead makes more sense; the change
proposed adds the same in mac80211.
Signed-off-by: Manikanta Pubbisetty <mpubbise@codeaurora.org>
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2018-07-11 00:12:53 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-03-26 12:14:31 +02:00
|
|
|
|
mac80211: add stop/start logic for software TXQs
Sometimes, it is required to stop the transmissions momentarily and
resume it later; stopping the txqs becomes very critical in scenarios where
the packet transmission has to be ceased completely. For example, during
the hardware restart, during off channel operations,
when initiating CSA(upon detecting a radar on the DFS channel), etc.
The TX queue stop/start logic in mac80211 works well in stopping the TX
when drivers make use of netdev queues, i.e, when Qdiscs in network layer
take care of traffic scheduling. Since the devices implementing
wake_tx_queue can run without Qdiscs, packets will be handed to mac80211
directly without queueing them in the netdev queues.
Also, mac80211 does not invoke any of the
netif_stop_*/netif_wake_* APIs if wake_tx_queue is implemented.
Since the queues are not stopped in this case, transmissions can continue
and this will impact negatively on the operation of the wireless device.
For example,
During hardware restart, we stop the netdev queues so that packets are
not sent to the driver. Since ath10k implements wake_tx_queue,
TX queues will not be stopped and packets might reach the hardware while
it is restarting; this can make hardware unresponsive and the only
possible option for recovery is to reboot the entire system.
There is another problem to this, it is observed that the packets
were sent on the DFS channel for a prolonged duration after radar
detection impacting the channel closing time.
We can still invoke netif stop/wake APIs when wake_tx_queue is implemented
but this could lead to packet drops in network layer; adding stop/start
logic for software TXQs in mac80211 instead makes more sense; the change
proposed adds the same in mac80211.
Signed-off-by: Manikanta Pubbisetty <mpubbise@codeaurora.org>
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2018-07-11 00:12:53 +05:30
|
|
|
|
2018-09-14 18:00:34 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-03-26 12:14:31 +02:00
|
|
|
|
mac80211: add stop/start logic for software TXQs
Sometimes, it is required to stop the transmissions momentarily and
resume it later; stopping the txqs becomes very critical in scenarios where
the packet transmission has to be ceased completely. For example, during
the hardware restart, during off channel operations,
when initiating CSA(upon detecting a radar on the DFS channel), etc.
The TX queue stop/start logic in mac80211 works well in stopping the TX
when drivers make use of netdev queues, i.e, when Qdiscs in network layer
take care of traffic scheduling. Since the devices implementing
wake_tx_queue can run without Qdiscs, packets will be handed to mac80211
directly without queueing them in the netdev queues.
Also, mac80211 does not invoke any of the
netif_stop_*/netif_wake_* APIs if wake_tx_queue is implemented.
Since the queues are not stopped in this case, transmissions can continue
and this will impact negatively on the operation of the wireless device.
For example,
During hardware restart, we stop the netdev queues so that packets are
not sent to the driver. Since ath10k implements wake_tx_queue,
TX queues will not be stopped and packets might reach the hardware while
it is restarting; this can make hardware unresponsive and the only
possible option for recovery is to reboot the entire system.
There is another problem to this, it is observed that the packets
were sent on the DFS channel for a prolonged duration after radar
detection impacting the channel closing time.
We can still invoke netif stop/wake APIs when wake_tx_queue is implemented
but this could lead to packet drops in network layer; adding stop/start
logic for software TXQs in mac80211 instead makes more sense; the change
proposed adds the same in mac80211.
Signed-off-by: Manikanta Pubbisetty <mpubbise@codeaurora.org>
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2018-07-11 00:12:53 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-12-30 13:18:49 +01:00
|
|
|
|
2026-03-26 12:14:31 +02:00
|
|
|
|
mac80211: add stop/start logic for software TXQs
Sometimes, it is required to stop the transmissions momentarily and
resume it later; stopping the txqs becomes very critical in scenarios where
the packet transmission has to be ceased completely. For example, during
the hardware restart, during off channel operations,
when initiating CSA(upon detecting a radar on the DFS channel), etc.
The TX queue stop/start logic in mac80211 works well in stopping the TX
when drivers make use of netdev queues, i.e, when Qdiscs in network layer
take care of traffic scheduling. Since the devices implementing
wake_tx_queue can run without Qdiscs, packets will be handed to mac80211
directly without queueing them in the netdev queues.
Also, mac80211 does not invoke any of the
netif_stop_*/netif_wake_* APIs if wake_tx_queue is implemented.
Since the queues are not stopped in this case, transmissions can continue
and this will impact negatively on the operation of the wireless device.
For example,
During hardware restart, we stop the netdev queues so that packets are
not sent to the driver. Since ath10k implements wake_tx_queue,
TX queues will not be stopped and packets might reach the hardware while
it is restarting; this can make hardware unresponsive and the only
possible option for recovery is to reboot the entire system.
There is another problem to this, it is observed that the packets
were sent on the DFS channel for a prolonged duration after radar
detection impacting the channel closing time.
We can still invoke netif stop/wake APIs when wake_tx_queue is implemented
but this could lead to packet drops in network layer; adding stop/start
logic for software TXQs in mac80211 instead makes more sense; the change
proposed adds the same in mac80211.
Signed-off-by: Manikanta Pubbisetty <mpubbise@codeaurora.org>
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2018-07-11 00:12:53 +05:30
|
|
|
|
|
|
|
|
|
2019-10-01 13:19:23 +02:00
|
|
|
|
2026-03-26 12:14:31 +02:00
|
|
|
|
2019-10-01 13:19:23 +02:00
|
|
|
|
mac80211: add stop/start logic for software TXQs
Sometimes, it is required to stop the transmissions momentarily and
resume it later; stopping the txqs becomes very critical in scenarios where
the packet transmission has to be ceased completely. For example, during
the hardware restart, during off channel operations,
when initiating CSA(upon detecting a radar on the DFS channel), etc.
The TX queue stop/start logic in mac80211 works well in stopping the TX
when drivers make use of netdev queues, i.e, when Qdiscs in network layer
take care of traffic scheduling. Since the devices implementing
wake_tx_queue can run without Qdiscs, packets will be handed to mac80211
directly without queueing them in the netdev queues.
Also, mac80211 does not invoke any of the
netif_stop_*/netif_wake_* APIs if wake_tx_queue is implemented.
Since the queues are not stopped in this case, transmissions can continue
and this will impact negatively on the operation of the wireless device.
For example,
During hardware restart, we stop the netdev queues so that packets are
not sent to the driver. Since ath10k implements wake_tx_queue,
TX queues will not be stopped and packets might reach the hardware while
it is restarting; this can make hardware unresponsive and the only
possible option for recovery is to reboot the entire system.
There is another problem to this, it is observed that the packets
were sent on the DFS channel for a prolonged duration after radar
detection impacting the channel closing time.
We can still invoke netif stop/wake APIs when wake_tx_queue is implemented
but this could lead to packet drops in network layer; adding stop/start
logic for software TXQs in mac80211 instead makes more sense; the change
proposed adds the same in mac80211.
Signed-off-by: Manikanta Pubbisetty <mpubbise@codeaurora.org>
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2018-07-11 00:12:53 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-03-26 12:14:31 +02:00
|
|
|
|
|
|
|
|
|
mac80211: add stop/start logic for software TXQs
Sometimes, it is required to stop the transmissions momentarily and
resume it later; stopping the txqs becomes very critical in scenarios where
the packet transmission has to be ceased completely. For example, during
the hardware restart, during off channel operations,
when initiating CSA(upon detecting a radar on the DFS channel), etc.
The TX queue stop/start logic in mac80211 works well in stopping the TX
when drivers make use of netdev queues, i.e, when Qdiscs in network layer
take care of traffic scheduling. Since the devices implementing
wake_tx_queue can run without Qdiscs, packets will be handed to mac80211
directly without queueing them in the netdev queues.
Also, mac80211 does not invoke any of the
netif_stop_*/netif_wake_* APIs if wake_tx_queue is implemented.
Since the queues are not stopped in this case, transmissions can continue
and this will impact negatively on the operation of the wireless device.
For example,
During hardware restart, we stop the netdev queues so that packets are
not sent to the driver. Since ath10k implements wake_tx_queue,
TX queues will not be stopped and packets might reach the hardware while
it is restarting; this can make hardware unresponsive and the only
possible option for recovery is to reboot the entire system.
There is another problem to this, it is observed that the packets
were sent on the DFS channel for a prolonged duration after radar
detection impacting the channel closing time.
We can still invoke netif stop/wake APIs when wake_tx_queue is implemented
but this could lead to packet drops in network layer; adding stop/start
logic for software TXQs in mac80211 instead makes more sense; the change
proposed adds the same in mac80211.
Signed-off-by: Manikanta Pubbisetty <mpubbise@codeaurora.org>
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2018-07-11 00:12:53 +05:30
|
|
|
|
2026-03-26 12:14:31 +02:00
|
|
|
|
|
|
|
|
|
mac80211: add stop/start logic for software TXQs
Sometimes, it is required to stop the transmissions momentarily and
resume it later; stopping the txqs becomes very critical in scenarios where
the packet transmission has to be ceased completely. For example, during
the hardware restart, during off channel operations,
when initiating CSA(upon detecting a radar on the DFS channel), etc.
The TX queue stop/start logic in mac80211 works well in stopping the TX
when drivers make use of netdev queues, i.e, when Qdiscs in network layer
take care of traffic scheduling. Since the devices implementing
wake_tx_queue can run without Qdiscs, packets will be handed to mac80211
directly without queueing them in the netdev queues.
Also, mac80211 does not invoke any of the
netif_stop_*/netif_wake_* APIs if wake_tx_queue is implemented.
Since the queues are not stopped in this case, transmissions can continue
and this will impact negatively on the operation of the wireless device.
For example,
During hardware restart, we stop the netdev queues so that packets are
not sent to the driver. Since ath10k implements wake_tx_queue,
TX queues will not be stopped and packets might reach the hardware while
it is restarting; this can make hardware unresponsive and the only
possible option for recovery is to reboot the entire system.
There is another problem to this, it is observed that the packets
were sent on the DFS channel for a prolonged duration after radar
detection impacting the channel closing time.
We can still invoke netif stop/wake APIs when wake_tx_queue is implemented
but this could lead to packet drops in network layer; adding stop/start
logic for software TXQs in mac80211 instead makes more sense; the change
proposed adds the same in mac80211.
Signed-off-by: Manikanta Pubbisetty <mpubbise@codeaurora.org>
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2018-07-11 00:12:53 +05:30
|
|
|
|
2026-03-26 12:14:31 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
mac80211: add stop/start logic for software TXQs
Sometimes, it is required to stop the transmissions momentarily and
resume it later; stopping the txqs becomes very critical in scenarios where
the packet transmission has to be ceased completely. For example, during
the hardware restart, during off channel operations,
when initiating CSA(upon detecting a radar on the DFS channel), etc.
The TX queue stop/start logic in mac80211 works well in stopping the TX
when drivers make use of netdev queues, i.e, when Qdiscs in network layer
take care of traffic scheduling. Since the devices implementing
wake_tx_queue can run without Qdiscs, packets will be handed to mac80211
directly without queueing them in the netdev queues.
Also, mac80211 does not invoke any of the
netif_stop_*/netif_wake_* APIs if wake_tx_queue is implemented.
Since the queues are not stopped in this case, transmissions can continue
and this will impact negatively on the operation of the wireless device.
For example,
During hardware restart, we stop the netdev queues so that packets are
not sent to the driver. Since ath10k implements wake_tx_queue,
TX queues will not be stopped and packets might reach the hardware while
it is restarting; this can make hardware unresponsive and the only
possible option for recovery is to reboot the entire system.
There is another problem to this, it is observed that the packets
were sent on the DFS channel for a prolonged duration after radar
detection impacting the channel closing time.
We can still invoke netif stop/wake APIs when wake_tx_queue is implemented
but this could lead to packet drops in network layer; adding stop/start
logic for software TXQs in mac80211 instead makes more sense; the change
proposed adds the same in mac80211.
Signed-off-by: Manikanta Pubbisetty <mpubbise@codeaurora.org>
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2018-07-11 00:12:53 +05:30
|
|
|
|
2019-10-01 13:19:23 +02:00
|
|
|
|
mac80211: add stop/start logic for software TXQs
Sometimes, it is required to stop the transmissions momentarily and
resume it later; stopping the txqs becomes very critical in scenarios where
the packet transmission has to be ceased completely. For example, during
the hardware restart, during off channel operations,
when initiating CSA(upon detecting a radar on the DFS channel), etc.
The TX queue stop/start logic in mac80211 works well in stopping the TX
when drivers make use of netdev queues, i.e, when Qdiscs in network layer
take care of traffic scheduling. Since the devices implementing
wake_tx_queue can run without Qdiscs, packets will be handed to mac80211
directly without queueing them in the netdev queues.
Also, mac80211 does not invoke any of the
netif_stop_*/netif_wake_* APIs if wake_tx_queue is implemented.
Since the queues are not stopped in this case, transmissions can continue
and this will impact negatively on the operation of the wireless device.
For example,
During hardware restart, we stop the netdev queues so that packets are
not sent to the driver. Since ath10k implements wake_tx_queue,
TX queues will not be stopped and packets might reach the hardware while
it is restarting; this can make hardware unresponsive and the only
possible option for recovery is to reboot the entire system.
There is another problem to this, it is observed that the packets
were sent on the DFS channel for a prolonged duration after radar
detection impacting the channel closing time.
We can still invoke netif stop/wake APIs when wake_tx_queue is implemented
but this could lead to packet drops in network layer; adding stop/start
logic for software TXQs in mac80211 instead makes more sense; the change
proposed adds the same in mac80211.
Signed-off-by: Manikanta Pubbisetty <mpubbise@codeaurora.org>
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2018-07-11 00:12:53 +05:30
|
|
|
|
2026-03-26 12:14:31 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-10-01 13:19:23 +02:00
|
|
|
|
mac80211: add stop/start logic for software TXQs
Sometimes, it is required to stop the transmissions momentarily and
resume it later; stopping the txqs becomes very critical in scenarios where
the packet transmission has to be ceased completely. For example, during
the hardware restart, during off channel operations,
when initiating CSA(upon detecting a radar on the DFS channel), etc.
The TX queue stop/start logic in mac80211 works well in stopping the TX
when drivers make use of netdev queues, i.e, when Qdiscs in network layer
take care of traffic scheduling. Since the devices implementing
wake_tx_queue can run without Qdiscs, packets will be handed to mac80211
directly without queueing them in the netdev queues.
Also, mac80211 does not invoke any of the
netif_stop_*/netif_wake_* APIs if wake_tx_queue is implemented.
Since the queues are not stopped in this case, transmissions can continue
and this will impact negatively on the operation of the wireless device.
For example,
During hardware restart, we stop the netdev queues so that packets are
not sent to the driver. Since ath10k implements wake_tx_queue,
TX queues will not be stopped and packets might reach the hardware while
it is restarting; this can make hardware unresponsive and the only
possible option for recovery is to reboot the entire system.
There is another problem to this, it is observed that the packets
were sent on the DFS channel for a prolonged duration after radar
detection impacting the channel closing time.
We can still invoke netif stop/wake APIs when wake_tx_queue is implemented
but this could lead to packet drops in network layer; adding stop/start
logic for software TXQs in mac80211 instead makes more sense; the change
proposed adds the same in mac80211.
Signed-off-by: Manikanta Pubbisetty <mpubbise@codeaurora.org>
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2018-07-11 00:12:53 +05:30
|
|
|
|
|
|
|
|
|
2019-10-01 13:19:23 +02:00
|
|
|
|
|
|
|
|
|
mac80211: add stop/start logic for software TXQs
Sometimes, it is required to stop the transmissions momentarily and
resume it later; stopping the txqs becomes very critical in scenarios where
the packet transmission has to be ceased completely. For example, during
the hardware restart, during off channel operations,
when initiating CSA(upon detecting a radar on the DFS channel), etc.
The TX queue stop/start logic in mac80211 works well in stopping the TX
when drivers make use of netdev queues, i.e, when Qdiscs in network layer
take care of traffic scheduling. Since the devices implementing
wake_tx_queue can run without Qdiscs, packets will be handed to mac80211
directly without queueing them in the netdev queues.
Also, mac80211 does not invoke any of the
netif_stop_*/netif_wake_* APIs if wake_tx_queue is implemented.
Since the queues are not stopped in this case, transmissions can continue
and this will impact negatively on the operation of the wireless device.
For example,
During hardware restart, we stop the netdev queues so that packets are
not sent to the driver. Since ath10k implements wake_tx_queue,
TX queues will not be stopped and packets might reach the hardware while
it is restarting; this can make hardware unresponsive and the only
possible option for recovery is to reboot the entire system.
There is another problem to this, it is observed that the packets
were sent on the DFS channel for a prolonged duration after radar
detection impacting the channel closing time.
We can still invoke netif stop/wake APIs when wake_tx_queue is implemented
but this could lead to packet drops in network layer; adding stop/start
logic for software TXQs in mac80211 instead makes more sense; the change
proposed adds the same in mac80211.
Signed-off-by: Manikanta Pubbisetty <mpubbise@codeaurora.org>
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2018-07-11 00:12:53 +05:30
|
|
|
|
|
|
|
|
|
2018-12-03 21:15:49 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
mac80211: add stop/start logic for software TXQs
Sometimes, it is required to stop the transmissions momentarily and
resume it later; stopping the txqs becomes very critical in scenarios where
the packet transmission has to be ceased completely. For example, during
the hardware restart, during off channel operations,
when initiating CSA(upon detecting a radar on the DFS channel), etc.
The TX queue stop/start logic in mac80211 works well in stopping the TX
when drivers make use of netdev queues, i.e, when Qdiscs in network layer
take care of traffic scheduling. Since the devices implementing
wake_tx_queue can run without Qdiscs, packets will be handed to mac80211
directly without queueing them in the netdev queues.
Also, mac80211 does not invoke any of the
netif_stop_*/netif_wake_* APIs if wake_tx_queue is implemented.
Since the queues are not stopped in this case, transmissions can continue
and this will impact negatively on the operation of the wireless device.
For example,
During hardware restart, we stop the netdev queues so that packets are
not sent to the driver. Since ath10k implements wake_tx_queue,
TX queues will not be stopped and packets might reach the hardware while
it is restarting; this can make hardware unresponsive and the only
possible option for recovery is to reboot the entire system.
There is another problem to this, it is observed that the packets
were sent on the DFS channel for a prolonged duration after radar
detection impacting the channel closing time.
We can still invoke netif stop/wake APIs when wake_tx_queue is implemented
but this could lead to packet drops in network layer; adding stop/start
logic for software TXQs in mac80211 instead makes more sense; the change
proposed adds the same in mac80211.
Signed-off-by: Manikanta Pubbisetty <mpubbise@codeaurora.org>
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2018-07-11 00:12:53 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-12-03 21:15:49 +02:00
|
|
|
|
mac80211: add stop/start logic for software TXQs
Sometimes, it is required to stop the transmissions momentarily and
resume it later; stopping the txqs becomes very critical in scenarios where
the packet transmission has to be ceased completely. For example, during
the hardware restart, during off channel operations,
when initiating CSA(upon detecting a radar on the DFS channel), etc.
The TX queue stop/start logic in mac80211 works well in stopping the TX
when drivers make use of netdev queues, i.e, when Qdiscs in network layer
take care of traffic scheduling. Since the devices implementing
wake_tx_queue can run without Qdiscs, packets will be handed to mac80211
directly without queueing them in the netdev queues.
Also, mac80211 does not invoke any of the
netif_stop_*/netif_wake_* APIs if wake_tx_queue is implemented.
Since the queues are not stopped in this case, transmissions can continue
and this will impact negatively on the operation of the wireless device.
For example,
During hardware restart, we stop the netdev queues so that packets are
not sent to the driver. Since ath10k implements wake_tx_queue,
TX queues will not be stopped and packets might reach the hardware while
it is restarting; this can make hardware unresponsive and the only
possible option for recovery is to reboot the entire system.
There is another problem to this, it is observed that the packets
were sent on the DFS channel for a prolonged duration after radar
detection impacting the channel closing time.
We can still invoke netif stop/wake APIs when wake_tx_queue is implemented
but this could lead to packet drops in network layer; adding stop/start
logic for software TXQs in mac80211 instead makes more sense; the change
proposed adds the same in mac80211.
Signed-off-by: Manikanta Pubbisetty <mpubbise@codeaurora.org>
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2018-07-11 00:12:53 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-12-03 21:15:49 +02:00
|
|
|
|
mac80211: add stop/start logic for software TXQs
Sometimes, it is required to stop the transmissions momentarily and
resume it later; stopping the txqs becomes very critical in scenarios where
the packet transmission has to be ceased completely. For example, during
the hardware restart, during off channel operations,
when initiating CSA(upon detecting a radar on the DFS channel), etc.
The TX queue stop/start logic in mac80211 works well in stopping the TX
when drivers make use of netdev queues, i.e, when Qdiscs in network layer
take care of traffic scheduling. Since the devices implementing
wake_tx_queue can run without Qdiscs, packets will be handed to mac80211
directly without queueing them in the netdev queues.
Also, mac80211 does not invoke any of the
netif_stop_*/netif_wake_* APIs if wake_tx_queue is implemented.
Since the queues are not stopped in this case, transmissions can continue
and this will impact negatively on the operation of the wireless device.
For example,
During hardware restart, we stop the netdev queues so that packets are
not sent to the driver. Since ath10k implements wake_tx_queue,
TX queues will not be stopped and packets might reach the hardware while
it is restarting; this can make hardware unresponsive and the only
possible option for recovery is to reboot the entire system.
There is another problem to this, it is observed that the packets
were sent on the DFS channel for a prolonged duration after radar
detection impacting the channel closing time.
We can still invoke netif stop/wake APIs when wake_tx_queue is implemented
but this could lead to packet drops in network layer; adding stop/start
logic for software TXQs in mac80211 instead makes more sense; the change
proposed adds the same in mac80211.
Signed-off-by: Manikanta Pubbisetty <mpubbise@codeaurora.org>
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2018-07-11 00:12:53 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-11-03 14:48:18 +05:30
|
|
|
|
2018-12-03 21:15:49 +02:00
|
|
|
|
2020-11-03 14:48:18 +05:30
|
|
|
|
|
|
|
|
|
2018-12-03 21:15:49 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-12-18 23:35:20 +02:00
|
|
|
|
2014-06-13 16:30:05 +03:00
|
|
|
|
2018-12-03 21:15:49 +02:00
|
|
|
|
|
|
|
|
|
2007-07-27 15:43:23 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-03-23 17:28:42 +01:00
|
|
|
|
|
|
|
|
|
2008-12-18 23:35:20 +02:00
|
|
|
|
2012-03-28 11:04:27 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-11-24 15:29:53 +01:00
|
|
|
|
2014-06-13 16:30:05 +03:00
|
|
|
|
2015-11-24 15:29:53 +01:00
|
|
|
|
2014-06-13 16:30:05 +03:00
|
|
|
|
2015-11-24 15:29:53 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-06-13 16:30:05 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
mac80211: fix aggregation for hardware with ampdu queues
Hardware with AMPDU queues currently has broken aggregation.
This patch fixes it by making all A-MPDUs go over the regular AC queues,
but keeping track of the hardware queues in mac80211. As a first rough
version, it actually stops the AC queue for extended periods of time,
which can be removed by adding buffering internal to mac80211, but is
currently not a huge problem because people rarely use multiple TIDs
that are in the same AC (and iwlwifi currently doesn't operate as AP).
This is a short-term fix, my current medium-term plan, which I hope to
execute soon as well, but am not sure can finish before .30, looks like
this:
1) rework the internal queuing layer in mac80211 that we use for
fragments if the driver stopped queue in the middle of a fragmented
frame to be able to queue more frames at once (rather than just a
single frame with its fragments)
2) instead of stopping the entire AC queue, queue up the frames in a
per-station/per-TID queue during aggregation session initiation,
when the session has come up take all those frames and put them
onto the queue from 1)
3) push the ampdu queue layer abstraction this patch introduces in
mac80211 into the driver, and remove the virtual queue stuff from
mac80211 again
This plan will probably also affect ath9k in that mac80211 queues the
frames instead of passing them down, even when there are no ampdu queues.
Signed-off-by: Johannes Berg <johannes@sipsolutions.net>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
2009-02-12 00:51:53 +01:00
|
|
|
|
2025-01-01 07:05:28 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
mac80211: fix aggregation for hardware with ampdu queues
Hardware with AMPDU queues currently has broken aggregation.
This patch fixes it by making all A-MPDUs go over the regular AC queues,
but keeping track of the hardware queues in mac80211. As a first rough
version, it actually stops the AC queue for extended periods of time,
which can be removed by adding buffering internal to mac80211, but is
currently not a huge problem because people rarely use multiple TIDs
that are in the same AC (and iwlwifi currently doesn't operate as AP).
This is a short-term fix, my current medium-term plan, which I hope to
execute soon as well, but am not sure can finish before .30, looks like
this:
1) rework the internal queuing layer in mac80211 that we use for
fragments if the driver stopped queue in the middle of a fragmented
frame to be able to queue more frames at once (rather than just a
single frame with its fragments)
2) instead of stopping the entire AC queue, queue up the frames in a
per-station/per-TID queue during aggregation session initiation,
when the session has come up take all those frames and put them
onto the queue from 1)
3) push the ampdu queue layer abstraction this patch introduces in
mac80211 into the driver, and remove the virtual queue stuff from
mac80211 again
This plan will probably also affect ath9k in that mac80211 queues the
frames instead of passing them down, even when there are no ampdu queues.
Signed-off-by: Johannes Berg <johannes@sipsolutions.net>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
2009-02-12 00:51:53 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-10-09 18:30:40 +02:00
|
|
|
|
2009-06-17 17:43:56 +02:00
|
|
|
|
mac80211: add stop/start logic for software TXQs
Sometimes, it is required to stop the transmissions momentarily and
resume it later; stopping the txqs becomes very critical in scenarios where
the packet transmission has to be ceased completely. For example, during
the hardware restart, during off channel operations,
when initiating CSA(upon detecting a radar on the DFS channel), etc.
The TX queue stop/start logic in mac80211 works well in stopping the TX
when drivers make use of netdev queues, i.e, when Qdiscs in network layer
take care of traffic scheduling. Since the devices implementing
wake_tx_queue can run without Qdiscs, packets will be handed to mac80211
directly without queueing them in the netdev queues.
Also, mac80211 does not invoke any of the
netif_stop_*/netif_wake_* APIs if wake_tx_queue is implemented.
Since the queues are not stopped in this case, transmissions can continue
and this will impact negatively on the operation of the wireless device.
For example,
During hardware restart, we stop the netdev queues so that packets are
not sent to the driver. Since ath10k implements wake_tx_queue,
TX queues will not be stopped and packets might reach the hardware while
it is restarting; this can make hardware unresponsive and the only
possible option for recovery is to reboot the entire system.
There is another problem to this, it is observed that the packets
were sent on the DFS channel for a prolonged duration after radar
detection impacting the channel closing time.
We can still invoke netif stop/wake APIs when wake_tx_queue is implemented
but this could lead to packet drops in network layer; adding stop/start
logic for software TXQs in mac80211 instead makes more sense; the change
proposed adds the same in mac80211.
Signed-off-by: Manikanta Pubbisetty <mpubbise@codeaurora.org>
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2018-07-11 00:12:53 +05:30
|
|
|
|
2018-12-03 21:15:49 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-10-09 18:30:40 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2007-07-27 15:43:23 +02:00
|
|
|
|
2008-12-18 23:35:20 +02:00
|
|
|
|
mac80211: fix aggregation for hardware with ampdu queues
Hardware with AMPDU queues currently has broken aggregation.
This patch fixes it by making all A-MPDUs go over the regular AC queues,
but keeping track of the hardware queues in mac80211. As a first rough
version, it actually stops the AC queue for extended periods of time,
which can be removed by adding buffering internal to mac80211, but is
currently not a huge problem because people rarely use multiple TIDs
that are in the same AC (and iwlwifi currently doesn't operate as AP).
This is a short-term fix, my current medium-term plan, which I hope to
execute soon as well, but am not sure can finish before .30, looks like
this:
1) rework the internal queuing layer in mac80211 that we use for
fragments if the driver stopped queue in the middle of a fragmented
frame to be able to queue more frames at once (rather than just a
single frame with its fragments)
2) instead of stopping the entire AC queue, queue up the frames in a
per-station/per-TID queue during aggregation session initiation,
when the session has come up take all those frames and put them
onto the queue from 1)
3) push the ampdu queue layer abstraction this patch introduces in
mac80211 into the driver, and remove the virtual queue stuff from
mac80211 again
This plan will probably also affect ath9k in that mac80211 queues the
frames instead of passing them down, even when there are no ampdu queues.
Signed-off-by: Johannes Berg <johannes@sipsolutions.net>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
2009-02-12 00:51:53 +01:00
|
|
|
|
2014-06-13 16:30:05 +03:00
|
|
|
|
|
|
|
|
|
2008-12-18 23:35:20 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-12-03 21:15:49 +02:00
|
|
|
|
2008-12-18 23:35:20 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-06-13 16:30:05 +03:00
|
|
|
|
|
|
|
|
|
2008-12-18 23:35:20 +02:00
|
|
|
|
2007-07-27 15:43:23 +02:00
|
|
|
|
|
|
|
|
|
2008-12-18 23:35:20 +02:00
|
|
|
|
2014-06-13 16:30:05 +03:00
|
|
|
|
|
|
|
|
|
2007-07-27 15:43:23 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-03-23 17:28:42 +01:00
|
|
|
|
|
|
|
|
|
mac80211: fix aggregation for hardware with ampdu queues
Hardware with AMPDU queues currently has broken aggregation.
This patch fixes it by making all A-MPDUs go over the regular AC queues,
but keeping track of the hardware queues in mac80211. As a first rough
version, it actually stops the AC queue for extended periods of time,
which can be removed by adding buffering internal to mac80211, but is
currently not a huge problem because people rarely use multiple TIDs
that are in the same AC (and iwlwifi currently doesn't operate as AP).
This is a short-term fix, my current medium-term plan, which I hope to
execute soon as well, but am not sure can finish before .30, looks like
this:
1) rework the internal queuing layer in mac80211 that we use for
fragments if the driver stopped queue in the middle of a fragmented
frame to be able to queue more frames at once (rather than just a
single frame with its fragments)
2) instead of stopping the entire AC queue, queue up the frames in a
per-station/per-TID queue during aggregation session initiation,
when the session has come up take all those frames and put them
onto the queue from 1)
3) push the ampdu queue layer abstraction this patch introduces in
mac80211 into the driver, and remove the virtual queue stuff from
mac80211 again
This plan will probably also affect ath9k in that mac80211 queues the
frames instead of passing them down, even when there are no ampdu queues.
Signed-off-by: Johannes Berg <johannes@sipsolutions.net>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
2009-02-12 00:51:53 +01:00
|
|
|
|
2014-06-13 16:30:05 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-03-28 11:04:27 +02:00
|
|
|
|
2025-01-01 07:05:28 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-12-30 13:18:49 +01:00
|
|
|
|
2007-07-27 15:43:23 +02:00
|
|
|
|
2008-12-18 23:35:20 +02:00
|
|
|
|
mac80211: fix aggregation for hardware with ampdu queues
Hardware with AMPDU queues currently has broken aggregation.
This patch fixes it by making all A-MPDUs go over the regular AC queues,
but keeping track of the hardware queues in mac80211. As a first rough
version, it actually stops the AC queue for extended periods of time,
which can be removed by adding buffering internal to mac80211, but is
currently not a huge problem because people rarely use multiple TIDs
that are in the same AC (and iwlwifi currently doesn't operate as AP).
This is a short-term fix, my current medium-term plan, which I hope to
execute soon as well, but am not sure can finish before .30, looks like
this:
1) rework the internal queuing layer in mac80211 that we use for
fragments if the driver stopped queue in the middle of a fragmented
frame to be able to queue more frames at once (rather than just a
single frame with its fragments)
2) instead of stopping the entire AC queue, queue up the frames in a
per-station/per-TID queue during aggregation session initiation,
when the session has come up take all those frames and put them
onto the queue from 1)
3) push the ampdu queue layer abstraction this patch introduces in
mac80211 into the driver, and remove the virtual queue stuff from
mac80211 again
This plan will probably also affect ath9k in that mac80211 queues the
frames instead of passing them down, even when there are no ampdu queues.
Signed-off-by: Johannes Berg <johannes@sipsolutions.net>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
2009-02-12 00:51:53 +01:00
|
|
|
|
2014-06-13 16:30:05 +03:00
|
|
|
|
|
|
|
|
|
2008-12-18 23:35:20 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-06-13 16:30:05 +03:00
|
|
|
|
2008-12-18 23:35:20 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-06-13 16:30:05 +03:00
|
|
|
|
|
|
|
|
|
2008-12-18 23:35:20 +02:00
|
|
|
|
2007-07-27 15:43:23 +02:00
|
|
|
|
|
|
|
|
|
2009-06-07 21:58:37 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-07-27 10:33:31 +02:00
|
|
|
|
2012-04-03 16:28:50 +02:00
|
|
|
|
2009-07-27 10:33:31 +02:00
|
|
|
|
|
|
|
|
|
2012-10-10 22:40:23 +02:00
|
|
|
|
2009-07-27 10:33:31 +02:00
|
|
|
|
|
|
|
|
|
2009-06-07 21:58:37 +02:00
|
|
|
|
|
|
|
|
|
2014-06-13 16:30:05 +03:00
|
|
|
|
|
|
|
|
|
2009-06-17 17:43:56 +02:00
|
|
|
|
2014-06-13 16:30:05 +03:00
|
|
|
|
2018-12-03 21:15:49 +02:00
|
|
|
|
2009-06-07 21:58:37 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-02-20 11:19:58 +01:00
|
|
|
|
|
|
|
|
|
2009-06-07 21:58:37 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-09-29 16:04:30 +02:00
|
|
|
|
2009-06-07 21:58:37 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-07-27 10:33:31 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-10-10 22:40:23 +02:00
|
|
|
|
2009-07-27 10:33:31 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-04-03 16:28:50 +02:00
|
|
|
|
2012-03-28 11:04:28 +02:00
|
|
|
|
|
|
|
|
|
2014-06-13 16:30:05 +03:00
|
|
|
|
|
|
|
|
|
2012-03-28 11:04:28 +02:00
|
|
|
|
2009-06-17 17:43:56 +02:00
|
|
|
|
2009-06-07 21:58:37 +02:00
|
|
|
|
|
|
|
|
|
2009-06-17 17:43:56 +02:00
|
|
|
|
2009-06-07 21:58:37 +02:00
|
|
|
|
2014-06-13 16:30:05 +03:00
|
|
|
|
2018-12-03 21:15:49 +02:00
|
|
|
|
2009-06-07 21:58:37 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-12-18 23:35:20 +02:00
|
|
|
|
2013-02-13 12:25:28 +01:00
|
|
|
|
2014-06-13 16:30:05 +03:00
|
|
|
|
|
|
|
|
|
2007-07-27 15:43:23 +02:00
|
|
|
|
2008-12-18 23:35:20 +02:00
|
|
|
|
|
|
|
|
|
2007-07-27 15:43:23 +02:00
|
|
|
|
|
|
|
|
|
2008-12-18 23:35:20 +02:00
|
|
|
|
|
|
|
|
|
2013-02-13 12:25:28 +01:00
|
|
|
|
2014-06-13 16:30:05 +03:00
|
|
|
|
2008-12-18 23:35:20 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-02-13 12:25:28 +01:00
|
|
|
|
2014-06-13 16:30:05 +03:00
|
|
|
|
|
|
|
|
|
2007-07-27 15:43:23 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-07-24 21:02:04 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-06-17 17:43:56 +02:00
|
|
|
|
|
|
|
|
|
mac80211: fix aggregation for hardware with ampdu queues
Hardware with AMPDU queues currently has broken aggregation.
This patch fixes it by making all A-MPDUs go over the regular AC queues,
but keeping track of the hardware queues in mac80211. As a first rough
version, it actually stops the AC queue for extended periods of time,
which can be removed by adding buffering internal to mac80211, but is
currently not a huge problem because people rarely use multiple TIDs
that are in the same AC (and iwlwifi currently doesn't operate as AP).
This is a short-term fix, my current medium-term plan, which I hope to
execute soon as well, but am not sure can finish before .30, looks like
this:
1) rework the internal queuing layer in mac80211 that we use for
fragments if the driver stopped queue in the middle of a fragmented
frame to be able to queue more frames at once (rather than just a
single frame with its fragments)
2) instead of stopping the entire AC queue, queue up the frames in a
per-station/per-TID queue during aggregation session initiation,
when the session has come up take all those frames and put them
onto the queue from 1)
3) push the ampdu queue layer abstraction this patch introduces in
mac80211 into the driver, and remove the virtual queue stuff from
mac80211 again
This plan will probably also affect ath9k in that mac80211 queues the
frames instead of passing them down, even when there are no ampdu queues.
Signed-off-by: Johannes Berg <johannes@sipsolutions.net>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
2009-02-12 00:51:53 +01:00
|
|
|
|
2009-03-23 17:28:42 +01:00
|
|
|
|
|
|
|
|
|
mac80211: fix aggregation for hardware with ampdu queues
Hardware with AMPDU queues currently has broken aggregation.
This patch fixes it by making all A-MPDUs go over the regular AC queues,
but keeping track of the hardware queues in mac80211. As a first rough
version, it actually stops the AC queue for extended periods of time,
which can be removed by adding buffering internal to mac80211, but is
currently not a huge problem because people rarely use multiple TIDs
that are in the same AC (and iwlwifi currently doesn't operate as AP).
This is a short-term fix, my current medium-term plan, which I hope to
execute soon as well, but am not sure can finish before .30, looks like
this:
1) rework the internal queuing layer in mac80211 that we use for
fragments if the driver stopped queue in the middle of a fragmented
frame to be able to queue more frames at once (rather than just a
single frame with its fragments)
2) instead of stopping the entire AC queue, queue up the frames in a
per-station/per-TID queue during aggregation session initiation,
when the session has come up take all those frames and put them
onto the queue from 1)
3) push the ampdu queue layer abstraction this patch introduces in
mac80211 into the driver, and remove the virtual queue stuff from
mac80211 again
This plan will probably also affect ath9k in that mac80211 queues the
frames instead of passing them down, even when there are no ampdu queues.
Signed-off-by: Johannes Berg <johannes@sipsolutions.net>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
2009-02-12 00:51:53 +01:00
|
|
|
|
2009-06-17 17:43:56 +02:00
|
|
|
|
2013-04-10 15:41:40 -07:00
|
|
|
|
|
|
|
|
|
2009-06-17 17:43:56 +02:00
|
|
|
|
|
|
|
|
|
2008-07-24 21:02:04 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-12-18 23:35:20 +02:00
|
|
|
|
2013-02-13 12:25:28 +01:00
|
|
|
|
2014-06-13 16:30:05 +03:00
|
|
|
|
|
|
|
|
|
2007-07-27 15:43:23 +02:00
|
|
|
|
2008-12-18 23:35:20 +02:00
|
|
|
|
|
|
|
|
|
2007-07-27 15:43:23 +02:00
|
|
|
|
|
|
|
|
|
2008-12-18 23:35:20 +02:00
|
|
|
|
|
|
|
|
|
2013-02-13 12:25:28 +01:00
|
|
|
|
2018-12-03 21:15:49 +02:00
|
|
|
|
2008-12-18 23:35:20 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-02-13 12:25:28 +01:00
|
|
|
|
2014-06-13 16:30:05 +03:00
|
|
|
|
|
|
|
|
|
2007-07-27 15:43:23 +02:00
|
|
|
|
|
|
|
|
|
2007-11-09 01:57:29 +01:00
|
|
|
|
2024-11-19 17:35:40 +02:00
|
|
|
|
2014-06-13 16:30:06 +03:00
|
|
|
|
|
|
|
|
|
2013-02-13 12:11:00 +01:00
|
|
|
|
2014-06-13 16:30:06 +03:00
|
|
|
|
2013-02-13 12:11:00 +01:00
|
|
|
|
2015-06-02 21:39:54 +02:00
|
|
|
|
2013-02-13 12:11:00 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-11-19 17:35:40 +02:00
|
|
|
|
|
|
|
|
|
2013-02-13 12:11:00 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-06-13 16:30:06 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-11-09 18:50:21 +02:00
|
|
|
|
|
|
|
|
|
2015-01-07 15:42:39 +02:00
|
|
|
|
2014-06-13 16:30:06 +03:00
|
|
|
|
2025-02-04 13:31:29 +01:00
|
|
|
|
2014-06-13 16:30:06 +03:00
|
|
|
|
|
|
|
|
|
2014-11-09 18:50:21 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-06-02 21:39:54 +02:00
|
|
|
|
2014-11-09 18:50:21 +02:00
|
|
|
|
2014-06-13 16:30:06 +03:00
|
|
|
|
2014-06-13 16:30:04 +03:00
|
|
|
|
2014-06-13 16:30:05 +03:00
|
|
|
|
|
|
|
|
|
2013-02-13 12:25:28 +01:00
|
|
|
|
2023-09-28 17:35:38 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-02-04 13:31:29 +01:00
|
|
|
|
|
|
|
|
|
2013-02-13 12:25:28 +01:00
|
|
|
|
2014-06-13 16:30:04 +03:00
|
|
|
|
2014-06-13 16:30:05 +03:00
|
|
|
|
|
|
|
|
|
2013-02-13 12:11:00 +01:00
|
|
|
|
|
|
|
|
|
2014-11-09 18:50:21 +02:00
|
|
|
|
2015-01-07 15:42:39 +02:00
|
|
|
|
2014-11-09 18:50:21 +02:00
|
|
|
|
2015-01-07 15:42:39 +02:00
|
|
|
|
2014-11-09 18:50:21 +02:00
|
|
|
|
|
|
|
|
|
2015-03-01 09:10:15 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2007-11-09 01:57:29 +01:00
|
|
|
|
|
|
|
|
|
2015-03-01 09:10:15 +02:00
|
|
|
|
2007-11-09 01:57:29 +01:00
|
|
|
|
2024-08-27 09:49:40 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2007-12-19 01:31:27 +01:00
|
|
|
|
2008-09-11 00:01:58 +02:00
|
|
|
|
2024-10-09 10:25:48 +02:00
|
|
|
|
|
|
|
|
|
2013-05-28 13:01:53 +02:00
|
|
|
|
|
|
|
|
|
2008-09-11 00:01:58 +02:00
|
|
|
|
2007-11-09 01:57:29 +01:00
|
|
|
|
2010-09-16 14:58:23 +02:00
|
|
|
|
2007-11-09 01:57:29 +01:00
|
|
|
|
|
|
|
|
|
2012-11-06 20:23:30 +01:00
|
|
|
|
2015-03-01 09:10:15 +02:00
|
|
|
|
2012-11-06 20:23:30 +01:00
|
|
|
|
2020-09-22 12:19:56 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-03-01 09:10:15 +02:00
|
|
|
|
2009-11-25 17:46:19 +01:00
|
|
|
|
2007-12-19 01:31:26 +01:00
|
|
|
|
2007-11-09 01:57:29 +01:00
|
|
|
|
2007-11-28 10:55:32 +01:00
|
|
|
|
2013-08-21 22:07:20 +02:00
|
|
|
|
|
|
|
|
|
2021-11-12 13:51:44 +01:00
|
|
|
|
2024-07-25 18:48:36 +02:00
|
|
|
|
2015-03-01 09:10:15 +02:00
|
|
|
|
2012-11-06 20:23:30 +01:00
|
|
|
|
2012-07-11 16:38:09 +02:00
|
|
|
|
2013-08-21 22:07:20 +02:00
|
|
|
|
2012-07-11 16:38:09 +02:00
|
|
|
|
2015-03-01 09:10:15 +02:00
|
|
|
|
2013-08-21 22:07:20 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-03-01 09:10:15 +02:00
|
|
|
|
2013-08-21 22:07:20 +02:00
|
|
|
|
|
|
|
|
|
2015-03-01 09:10:15 +02:00
|
|
|
|
2013-08-21 22:07:20 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-03-01 09:10:15 +02:00
|
|
|
|
|
|
|
|
|
2007-11-28 10:55:32 +01:00
|
|
|
|
2007-11-09 01:57:29 +01:00
|
|
|
|
2008-05-10 13:40:49 +02:00
|
|
|
|
2008-09-08 16:40:36 +02:00
|
|
|
|
2026-01-08 14:34:31 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-08-21 22:07:20 +02:00
|
|
|
|
2026-01-08 14:34:31 +01:00
|
|
|
|
|
|
|
|
|
2013-08-21 22:07:20 +02:00
|
|
|
|
|
|
|
|
|
2021-01-22 16:19:43 +01:00
|
|
|
|
2013-08-21 22:07:20 +02:00
|
|
|
|
2026-01-08 14:34:31 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-08-21 22:07:20 +02:00
|
|
|
|
2026-01-08 14:34:31 +01:00
|
|
|
|
2013-08-21 22:07:20 +02:00
|
|
|
|
2014-10-22 12:30:59 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-08-05 17:40:23 -07:00
|
|
|
|
|
|
|
|
|
2014-10-22 12:30:59 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-01-08 14:34:32 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-08-05 17:40:23 -07:00
|
|
|
|
|
|
|
|
|
2026-01-08 14:34:32 +01:00
|
|
|
|
2024-08-05 17:40:23 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-01-08 14:34:32 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-08-05 17:40:23 -07:00
|
|
|
|
2026-01-08 14:34:32 +01:00
|
|
|
|
2024-08-05 17:40:23 -07:00
|
|
|
|
2013-11-13 13:37:47 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-03-12 08:53:24 +02:00
|
|
|
|
|
|
|
|
|
2015-06-10 20:18:55 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-04-09 12:40:19 +03:00
|
|
|
|
2015-03-12 08:53:24 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-07-29 20:08:07 -04:00
|
|
|
|
|
|
|
|
|
2015-01-22 23:32:46 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-07-29 20:08:07 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-01-22 23:32:46 +02:00
|
|
|
|
|
|
|
|
|
2009-11-19 14:29:39 +01:00
|
|
|
|
2015-01-22 23:32:46 +02:00
|
|
|
|
2009-07-29 20:08:07 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-03-28 13:24:10 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-08-22 13:52:21 +02:00
|
|
|
|
2018-03-28 13:24:10 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
wifi: mac80211: move some future per-link data to bss_conf
To add MLD, reuse the bss_conf structure later for per-link
information, so move some things into it that are per link.
Most transformations were done with the following spatch:
@@
expression sdata;
identifier var = { chanctx_conf, mu_mimo_owner, csa_active, color_change_active, color_change_color };
@@
-sdata->vif.var
+sdata->vif.bss_conf.var
@@
struct ieee80211_vif *vif;
identifier var = { chanctx_conf, mu_mimo_owner, csa_active, color_change_active, color_change_color };
@@
-vif->var
+vif->bss_conf.var
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2022-05-10 13:26:44 +02:00
|
|
|
|
2018-03-28 13:24:10 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-08-22 13:52:21 +02:00
|
|
|
|
2018-03-28 13:24:10 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-08-22 13:52:21 +02:00
|
|
|
|
2018-03-28 13:24:10 +03:00
|
|
|
|
2018-08-22 13:52:21 +02:00
|
|
|
|
2018-03-28 13:24:10 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-08-31 11:31:04 +03:00
|
|
|
|
2018-03-28 13:24:10 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-06-24 15:40:11 +02:00
|
|
|
|
2015-10-22 17:46:04 +02:00
|
|
|
|
2008-09-09 12:56:01 +02:00
|
|
|
|
2022-06-24 15:40:11 +02:00
|
|
|
|
2008-09-09 12:56:01 +02:00
|
|
|
|
|
|
|
|
|
2012-07-26 17:24:39 +02:00
|
|
|
|
2012-03-28 11:04:25 +02:00
|
|
|
|
2015-10-22 17:46:04 +02:00
|
|
|
|
2014-11-03 10:33:19 +01:00
|
|
|
|
2009-05-07 16:16:24 +02:00
|
|
|
|
2008-09-09 12:56:01 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-03-28 11:04:25 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-09-09 12:56:01 +02:00
|
|
|
|
|
|
|
|
|
2012-07-26 17:24:39 +02:00
|
|
|
|
2022-06-24 15:40:11 +02:00
|
|
|
|
2012-07-26 17:24:39 +02:00
|
|
|
|
2016-04-12 15:56:15 +02:00
|
|
|
|
2022-07-12 10:49:23 +02:00
|
|
|
|
2012-07-26 17:24:39 +02:00
|
|
|
|
2008-09-09 12:56:01 +02:00
|
|
|
|
2014-11-03 10:33:19 +01:00
|
|
|
|
|
|
|
|
|
2013-09-09 23:03:41 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-09-09 12:56:01 +02:00
|
|
|
|
2024-09-13 11:49:19 +03:00
|
|
|
|
2013-09-09 23:03:41 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-05-30 10:56:46 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-11-03 10:33:19 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-05-30 10:56:46 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-11-03 10:33:19 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-05-30 10:56:46 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-11-03 10:33:19 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-05-30 10:56:46 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-11-03 10:33:19 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-05-30 10:56:46 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-11-03 10:33:19 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-05-30 10:56:46 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-05-07 16:16:24 +02:00
|
|
|
|
2018-03-28 13:24:10 +03:00
|
|
|
|
2008-09-09 12:56:01 +02:00
|
|
|
|
2010-01-12 10:42:31 +02:00
|
|
|
|
|
|
|
|
|
2022-06-24 15:40:11 +02:00
|
|
|
|
|
|
|
|
|
2009-05-07 16:16:24 +02:00
|
|
|
|
2010-03-29 12:18:34 +02:00
|
|
|
|
2012-06-18 20:07:15 +02:00
|
|
|
|
2016-09-20 17:31:14 +03:00
|
|
|
|
|
|
|
|
|
2022-06-24 15:40:11 +02:00
|
|
|
|
2012-03-02 15:56:59 +01:00
|
|
|
|
2022-06-24 15:40:11 +02:00
|
|
|
|
2022-05-24 10:55:56 +02:00
|
|
|
|
2010-07-23 10:47:11 +05:30
|
|
|
|
2008-09-09 12:56:01 +02:00
|
|
|
|
2008-09-09 15:07:09 +02:00
|
|
|
|
2009-02-15 12:44:28 +01:00
|
|
|
|
2012-09-30 19:29:37 +03:00
|
|
|
|
2013-02-12 16:43:19 +01:00
|
|
|
|
2013-01-29 15:02:27 +01:00
|
|
|
|
|
|
|
|
|
2009-02-15 12:44:28 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-08 16:36:08 +03:00
|
|
|
|
2022-07-12 13:38:07 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
wifi: mac80211: Check for MLE before appending in Authentication frame
Currently, in MLO connections, userspace constructs most of the
Authentication frame body, excluding the Multi-Link element (MLE),
which mac80211 appends later in ieee80211_send_auth(). At present,
mac80211 always adds the MLE itself, since userspace
(e.g. wpa_supplicant) does not yet include it.
However, for new authentication protocols such as Enhanced Privacy
Protection Key Exchange (EPPKE), as specified in
"IEEE P802.11bi/D3.0 section 12.16.9", the MLE must be included in
userspace so that the Message Integrity Code (MIC) can be computed
correctly over the complete frame body. Table 9-71 specifies that
the MIC is mandatory. If mac80211 appends the MLE again, the
Authentication frame becomes invalid.
Add a check in ieee80211_send_auth() to detect whether the MLE is
already present in the Authentication frame body before appending.
Skip the append if the MLE exists, otherwise add it as before.
Signed-off-by: Kavita Kavita <kavita.kavita@oss.qualcomm.com>
Link: https://patch.msgid.link/20260114111900.2196941-7-kavita.kavita@oss.qualcomm.com
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2026-01-14 16:48:57 +05:30
|
|
|
|
cfg80211: rework key operation
This reworks the key operation in cfg80211, and now only
allows, from userspace, configuring keys (via nl80211)
after the connection has been established (in managed
mode), the IBSS been joined (in IBSS mode), at any time
(in AP[_VLAN] modes) or never for all the other modes.
In order to do shared key authentication correctly, it
is now possible to give a WEP key to the AUTH command.
To configure static WEP keys, these are given to the
CONNECT or IBSS_JOIN command directly, for a userspace
SME it is assumed it will configure it properly after
the connection has been established.
Since mac80211 used to check the default key in IBSS
mode to see whether or not the network is protected,
it needs an update in that area, as well as an update
to make use of the WEP key passed to auth() for shared
key authentication.
Signed-off-by: Johannes Berg <johannes@sipsolutions.net>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
2009-07-08 14:22:54 +02:00
|
|
|
|
2009-02-15 12:44:28 +01:00
|
|
|
|
wifi: mac80211: Check for MLE before appending in Authentication frame
Currently, in MLO connections, userspace constructs most of the
Authentication frame body, excluding the Multi-Link element (MLE),
which mac80211 appends later in ieee80211_send_auth(). At present,
mac80211 always adds the MLE itself, since userspace
(e.g. wpa_supplicant) does not yet include it.
However, for new authentication protocols such as Enhanced Privacy
Protection Key Exchange (EPPKE), as specified in
"IEEE P802.11bi/D3.0 section 12.16.9", the MLE must be included in
userspace so that the Message Integrity Code (MIC) can be computed
correctly over the complete frame body. Table 9-71 specifies that
the MIC is mandatory. If mac80211 appends the MLE again, the
Authentication frame becomes invalid.
Add a check in ieee80211_send_auth() to detect whether the MLE is
already present in the Authentication frame body before appending.
Skip the append if the MLE exists, otherwise add it as before.
Signed-off-by: Kavita Kavita <kavita.kavita@oss.qualcomm.com>
Link: https://patch.msgid.link/20260114111900.2196941-7-kavita.kavita@oss.qualcomm.com
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2026-01-14 16:48:57 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-07-12 13:38:07 +02:00
|
|
|
|
2013-09-24 10:33:01 +08:00
|
|
|
|
2014-06-10 20:00:08 +03:00
|
|
|
|
2022-07-12 13:38:07 +02:00
|
|
|
|
wifi: mac80211: Check for MLE before appending in Authentication frame
Currently, in MLO connections, userspace constructs most of the
Authentication frame body, excluding the Multi-Link element (MLE),
which mac80211 appends later in ieee80211_send_auth(). At present,
mac80211 always adds the MLE itself, since userspace
(e.g. wpa_supplicant) does not yet include it.
However, for new authentication protocols such as Enhanced Privacy
Protection Key Exchange (EPPKE), as specified in
"IEEE P802.11bi/D3.0 section 12.16.9", the MLE must be included in
userspace so that the Message Integrity Code (MIC) can be computed
correctly over the complete frame body. Table 9-71 specifies that
the MIC is mandatory. If mac80211 appends the MLE again, the
Authentication frame becomes invalid.
Add a check in ieee80211_send_auth() to detect whether the MLE is
already present in the Authentication frame body before appending.
Skip the append if the MLE exists, otherwise add it as before.
Signed-off-by: Kavita Kavita <kavita.kavita@oss.qualcomm.com>
Link: https://patch.msgid.link/20260114111900.2196941-7-kavita.kavita@oss.qualcomm.com
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2026-01-14 16:48:57 +05:30
|
|
|
|
2011-08-29 14:17:31 -07:00
|
|
|
|
2009-02-15 12:44:28 +01:00
|
|
|
|
2011-08-29 14:17:31 -07:00
|
|
|
|
2014-06-10 20:00:08 +03:00
|
|
|
|
2009-02-15 12:44:28 +01:00
|
|
|
|
networking: convert many more places to skb_put_zero()
There were many places that my previous spatch didn't find,
as pointed out by yuan linyu in various patches.
The following spatch found many more and also removes the
now unnecessary casts:
@@
identifier p, p2;
expression len;
expression skb;
type t, t2;
@@
(
-p = skb_put(skb, len);
+p = skb_put_zero(skb, len);
|
-p = (t)skb_put(skb, len);
+p = skb_put_zero(skb, len);
)
... when != p
(
p2 = (t2)p;
-memset(p2, 0, len);
|
-memset(p, 0, len);
)
@@
type t, t2;
identifier p, p2;
expression skb;
@@
t *p;
...
(
-p = skb_put(skb, sizeof(t));
+p = skb_put_zero(skb, sizeof(t));
|
-p = (t *)skb_put(skb, sizeof(t));
+p = skb_put_zero(skb, sizeof(t));
)
... when != p
(
p2 = (t2)p;
-memset(p2, 0, sizeof(*p));
|
-memset(p, 0, sizeof(*p));
)
@@
expression skb, len;
@@
-memset(skb_put(skb, len), 0, len);
+skb_put_zero(skb, len);
Apply it to the tree (with one manual fixup to keep the
comment in vxlan.c, which spatch removed.)
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2017-06-16 14:29:19 +02:00
|
|
|
|
2009-02-15 12:44:28 +01:00
|
|
|
|
|
|
|
|
|
2012-01-09 19:43:06 +01:00
|
|
|
|
2009-11-25 17:46:19 +01:00
|
|
|
|
2009-02-15 12:44:28 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-09-30 19:29:37 +03:00
|
|
|
|
2009-02-15 12:44:28 +01:00
|
|
|
|
networking: introduce and use skb_put_data()
A common pattern with skb_put() is to just want to memcpy()
some data into the new space, introduce skb_put_data() for
this.
An spatch similar to the one for skb_put_zero() converts many
of the places using it:
@@
identifier p, p2;
expression len, skb, data;
type t, t2;
@@
(
-p = skb_put(skb, len);
+p = skb_put_data(skb, data, len);
|
-p = (t)skb_put(skb, len);
+p = skb_put_data(skb, data, len);
)
(
p2 = (t2)p;
-memcpy(p2, data, len);
|
-memcpy(p, data, len);
)
@@
type t, t2;
identifier p, p2;
expression skb, data;
@@
t *p;
...
(
-p = skb_put(skb, sizeof(t));
+p = skb_put_data(skb, data, sizeof(t));
|
-p = (t *)skb_put(skb, sizeof(t));
+p = skb_put_data(skb, data, sizeof(t));
)
(
p2 = (t2)p;
-memcpy(p2, data, sizeof(*p));
|
-memcpy(p, data, sizeof(*p));
)
@@
expression skb, len, data;
@@
-memcpy(skb_put(skb, len), data, len);
+skb_put_data(skb, data, len);
(again, manually post-processed to retain some comments)
Reviewed-by: Stephen Hemminger <stephen@networkplumber.org>
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2017-06-16 14:29:20 +02:00
|
|
|
|
wifi: mac80211: Check for MLE before appending in Authentication frame
Currently, in MLO connections, userspace constructs most of the
Authentication frame body, excluding the Multi-Link element (MLE),
which mac80211 appends later in ieee80211_send_auth(). At present,
mac80211 always adds the MLE itself, since userspace
(e.g. wpa_supplicant) does not yet include it.
However, for new authentication protocols such as Enhanced Privacy
Protection Key Exchange (EPPKE), as specified in
"IEEE P802.11bi/D3.0 section 12.16.9", the MLE must be included in
userspace so that the Message Integrity Code (MIC) can be computed
correctly over the complete frame body. Table 9-71 specifies that
the MIC is mandatory. If mac80211 appends the MLE again, the
Authentication frame becomes invalid.
Add a check in ieee80211_send_auth() to detect whether the MLE is
already present in the Authentication frame body before appending.
Skip the append if the MLE exists, otherwise add it as before.
Signed-off-by: Kavita Kavita <kavita.kavita@oss.qualcomm.com>
Link: https://patch.msgid.link/20260114111900.2196941-7-kavita.kavita@oss.qualcomm.com
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2026-01-14 16:48:57 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-07-12 13:38:07 +02:00
|
|
|
|
wifi: mac80211: Check for MLE before appending in Authentication frame
Currently, in MLO connections, userspace constructs most of the
Authentication frame body, excluding the Multi-Link element (MLE),
which mac80211 appends later in ieee80211_send_auth(). At present,
mac80211 always adds the MLE itself, since userspace
(e.g. wpa_supplicant) does not yet include it.
However, for new authentication protocols such as Enhanced Privacy
Protection Key Exchange (EPPKE), as specified in
"IEEE P802.11bi/D3.0 section 12.16.9", the MLE must be included in
userspace so that the Message Integrity Code (MIC) can be computed
correctly over the complete frame body. Table 9-71 specifies that
the MIC is mandatory. If mac80211 appends the MLE again, the
Authentication frame becomes invalid.
Add a check in ieee80211_send_auth() to detect whether the MLE is
already present in the Authentication frame body before appending.
Skip the append if the MLE exists, otherwise add it as before.
Signed-off-by: Kavita Kavita <kavita.kavita@oss.qualcomm.com>
Link: https://patch.msgid.link/20260114111900.2196941-7-kavita.kavita@oss.qualcomm.com
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2026-01-14 16:48:57 +05:30
|
|
|
|
2009-02-15 12:44:28 +01:00
|
|
|
|
cfg80211: rework key operation
This reworks the key operation in cfg80211, and now only
allows, from userspace, configuring keys (via nl80211)
after the connection has been established (in managed
mode), the IBSS been joined (in IBSS mode), at any time
(in AP[_VLAN] modes) or never for all the other modes.
In order to do shared key authentication correctly, it
is now possible to give a WEP key to the AUTH command.
To configure static WEP keys, these are given to the
CONNECT or IBSS_JOIN command directly, for a userspace
SME it is assumed it will configure it properly after
the connection has been established.
Since mac80211 used to check the default key in IBSS
mode to see whether or not the network is protected,
it needs an update in that area, as well as an update
to make use of the WEP key passed to auth() for shared
key authentication.
Signed-off-by: Johannes Berg <johannes@sipsolutions.net>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
2009-07-08 14:22:54 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-06-18 13:41:33 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
cfg80211: rework key operation
This reworks the key operation in cfg80211, and now only
allows, from userspace, configuring keys (via nl80211)
after the connection has been established (in managed
mode), the IBSS been joined (in IBSS mode), at any time
(in AP[_VLAN] modes) or never for all the other modes.
In order to do shared key authentication correctly, it
is now possible to give a WEP key to the AUTH command.
To configure static WEP keys, these are given to the
CONNECT or IBSS_JOIN command directly, for a userspace
SME it is assumed it will configure it properly after
the connection has been established.
Since mac80211 used to check the default key in IBSS
mode to see whether or not the network is protected,
it needs an update in that area, as well as an update
to make use of the WEP key passed to auth() for shared
key authentication.
Signed-off-by: Johannes Berg <johannes@sipsolutions.net>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
2009-07-08 14:22:54 +02:00
|
|
|
|
|
|
|
|
|
2013-01-29 15:02:27 +01:00
|
|
|
|
|
|
|
|
|
2009-11-18 18:42:05 +01:00
|
|
|
|
2009-02-15 12:44:28 +01:00
|
|
|
|
|
|
|
|
|
2012-09-07 13:28:52 +02:00
|
|
|
|
2019-08-30 14:24:51 +03:00
|
|
|
|
|
|
|
|
|
2012-09-07 13:28:52 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-08-30 14:24:51 +03:00
|
|
|
|
2012-09-07 13:28:52 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
networking: introduce and use skb_put_data()
A common pattern with skb_put() is to just want to memcpy()
some data into the new space, introduce skb_put_data() for
this.
An spatch similar to the one for skb_put_zero() converts many
of the places using it:
@@
identifier p, p2;
expression len, skb, data;
type t, t2;
@@
(
-p = skb_put(skb, len);
+p = skb_put_data(skb, data, len);
|
-p = (t)skb_put(skb, len);
+p = skb_put_data(skb, data, len);
)
(
p2 = (t2)p;
-memcpy(p2, data, len);
|
-memcpy(p, data, len);
)
@@
type t, t2;
identifier p, p2;
expression skb, data;
@@
t *p;
...
(
-p = skb_put(skb, sizeof(t));
+p = skb_put_data(skb, data, sizeof(t));
|
-p = (t *)skb_put(skb, sizeof(t));
+p = skb_put_data(skb, data, sizeof(t));
)
(
p2 = (t2)p;
-memcpy(p2, data, sizeof(*p));
|
-memcpy(p, data, sizeof(*p));
)
@@
expression skb, len, data;
@@
-memcpy(skb_put(skb, len), data, len);
+skb_put_data(skb, data, len);
(again, manually post-processed to retain some comments)
Reviewed-by: Stephen Hemminger <stephen@networkplumber.org>
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2017-06-16 14:29:20 +02:00
|
|
|
|
2012-09-07 13:28:52 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-01-29 20:19:33 +01:00
|
|
|
|
|
|
|
|
|
2020-05-28 21:34:39 +02:00
|
|
|
|
2024-01-29 20:19:33 +01:00
|
|
|
|
|
|
|
|
|
2020-05-28 21:34:39 +02:00
|
|
|
|
2024-01-29 20:19:33 +01:00
|
|
|
|
|
|
|
|
|
2020-05-28 21:34:39 +02:00
|
|
|
|
2024-01-29 20:19:33 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-05-28 21:34:39 +02:00
|
|
|
|
|
|
|
|
|
2024-01-29 20:19:33 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-04-01 11:58:36 +02:00
|
|
|
|
2020-05-28 21:34:39 +02:00
|
|
|
|
2009-04-01 11:58:36 +02:00
|
|
|
|
2024-01-29 20:19:33 +01:00
|
|
|
|
2014-02-05 15:21:13 +02:00
|
|
|
|
2014-11-24 15:49:44 +01:00
|
|
|
|
2009-04-01 11:58:36 +02:00
|
|
|
|
2014-02-05 15:21:13 +02:00
|
|
|
|
|
|
|
|
|
2009-10-27 20:59:55 +01:00
|
|
|
|
2012-07-09 19:57:28 +03:00
|
|
|
|
|
|
|
|
|
2009-04-01 11:58:36 +02:00
|
|
|
|
2023-02-23 16:25:12 +13:00
|
|
|
|
2024-01-29 20:19:33 +01:00
|
|
|
|
|
|
|
|
|
2023-02-23 16:25:12 +13:00
|
|
|
|
2025-03-29 22:14:20 +01:00
|
|
|
|
2024-03-01 17:54:51 +01:00
|
|
|
|
2024-01-29 20:19:33 +01:00
|
|
|
|
|
|
|
|
|
2009-04-01 11:58:36 +02:00
|
|
|
|
2009-12-23 13:15:38 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-02-05 15:21:13 +02:00
|
|
|
|
2024-01-29 20:19:33 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-02-05 15:21:13 +02:00
|
|
|
|
2009-12-23 13:15:38 +01:00
|
|
|
|
2009-04-01 11:58:36 +02:00
|
|
|
|
2025-03-29 22:14:20 +01:00
|
|
|
|
2024-03-01 17:54:51 +01:00
|
|
|
|
2024-01-29 20:19:33 +01:00
|
|
|
|
|
|
|
|
|
2009-12-23 13:15:38 +01:00
|
|
|
|
2016-04-12 15:56:15 +02:00
|
|
|
|
2024-01-29 20:19:33 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-08-28 19:37:51 +03:00
|
|
|
|
|
|
|
|
|
2018-05-28 15:47:41 +02:00
|
|
|
|
2024-01-29 20:19:33 +01:00
|
|
|
|
2018-05-28 15:47:41 +02:00
|
|
|
|
2009-12-23 13:15:38 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-08-05 11:44:32 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-12-23 13:15:38 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-02-05 15:21:13 +02:00
|
|
|
|
2024-01-29 20:19:33 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-02-05 15:21:13 +02:00
|
|
|
|
2009-04-01 11:58:36 +02:00
|
|
|
|
|
|
|
|
|
2012-11-29 12:45:18 +01:00
|
|
|
|
2024-01-29 20:19:33 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-11-29 12:45:18 +01:00
|
|
|
|
2009-03-31 12:12:07 +02:00
|
|
|
|
2014-02-04 09:48:34 +01:00
|
|
|
|
2009-12-23 13:15:38 +01:00
|
|
|
|
2014-02-04 09:48:34 +01:00
|
|
|
|
2017-08-05 11:44:32 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-02-04 09:48:34 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-08-05 11:44:29 +03:00
|
|
|
|
2017-08-05 11:44:32 +03:00
|
|
|
|
2014-02-04 09:48:34 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-02-05 15:21:13 +02:00
|
|
|
|
2024-01-29 20:19:33 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-02-05 15:21:13 +02:00
|
|
|
|
2009-04-01 11:58:36 +02:00
|
|
|
|
|
|
|
|
|
2014-11-24 15:49:44 +01:00
|
|
|
|
|
|
|
|
|
2015-01-01 13:43:17 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-11-24 15:49:44 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-01-29 20:19:33 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-11-29 12:45:18 +01:00
|
|
|
|
2012-07-02 11:25:12 +00:00
|
|
|
|
2018-06-09 09:14:44 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-01-29 20:19:33 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-06-09 09:14:44 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-01-29 20:19:35 +01:00
|
|
|
|
2021-06-18 13:41:40 +03:00
|
|
|
|
2024-01-29 20:19:35 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-06-18 13:41:42 +03:00
|
|
|
|
2020-05-28 21:34:39 +02:00
|
|
|
|
2024-01-29 20:19:36 +01:00
|
|
|
|
2022-02-14 17:30:01 +01:00
|
|
|
|
|
|
|
|
|
2024-01-29 20:19:36 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-02-14 17:30:01 +01:00
|
|
|
|
|
|
|
|
|
2024-01-29 20:19:33 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-06-09 09:14:44 +03:00
|
|
|
|
2026-01-30 16:21:07 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-06-09 09:14:44 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-01-29 20:19:33 +01:00
|
|
|
|
2009-04-01 11:58:36 +02:00
|
|
|
|
|
|
|
|
|
2024-01-29 20:19:33 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-05-28 21:34:39 +02:00
|
|
|
|
2014-02-05 15:21:13 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-05-28 15:47:38 +02:00
|
|
|
|
|
|
|
|
|
2014-02-05 15:21:13 +02:00
|
|
|
|
2024-01-29 20:19:33 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-02-05 15:21:13 +02:00
|
|
|
|
2024-01-29 20:19:33 +01:00
|
|
|
|
|
|
|
|
|
2014-02-05 15:21:13 +02:00
|
|
|
|
2024-01-29 20:19:33 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-04-12 15:56:15 +02:00
|
|
|
|
2024-01-29 20:19:33 +01:00
|
|
|
|
|
|
|
|
|
2014-02-05 15:21:13 +02:00
|
|
|
|
2024-01-29 20:19:33 +01:00
|
|
|
|
|
|
|
|
|
2014-02-05 15:21:13 +02:00
|
|
|
|
2024-01-29 20:19:33 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-02-05 15:21:13 +02:00
|
|
|
|
2010-11-11 08:50:18 +02:00
|
|
|
|
2014-06-12 22:24:31 +02:00
|
|
|
|
|
|
|
|
|
2012-07-23 14:53:27 +02:00
|
|
|
|
2010-11-11 08:50:18 +02:00
|
|
|
|
2011-06-23 09:00:11 -08:00
|
|
|
|
2018-05-28 15:47:38 +02:00
|
|
|
|
2009-02-15 12:44:28 +01:00
|
|
|
|
|
|
|
|
|
2013-07-08 16:55:53 +02:00
|
|
|
|
2009-02-15 12:44:28 +01:00
|
|
|
|
|
|
|
|
|
2016-04-12 15:56:15 +02:00
|
|
|
|
2014-02-05 15:21:13 +02:00
|
|
|
|
2009-02-15 12:44:28 +01:00
|
|
|
|
2011-06-23 09:00:11 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
wifi: mac80211: introduce 'channel request'
For channel contexts, mac80211 currently uses the cfg80211
chandef struct (control channel, center freq(s), width) to
define towards drivers and internally how these behave. In
fact, there are _two_ such structs used, where the min_def
can reduce bandwidth according to the stations connected.
Unfortunately, with EHT this is longer be sufficient, at
least not for all hardware. EHT requires that non-AP STAs
that are connected to an AP with a lower bandwidth than it
(the AP) advertises (e.g. 160 MHz STA connected to 320 MHz
AP) still be able to receive downlink OFDMA and respond to
trigger frames for uplink OFDMA that specify the position
and bandwidth for the non-AP STA relative to the channel
the AP is using. Therefore, they need to be aware of this,
and at least for some hardware (e.g. Intel) this awareness
is in the hardware. As a result, use of the "same" channel
may need to be split over two channel contexts where they
differ by the AP being used.
As a first step, introduce a concept of a channel request
('chanreq') for each interface, to control the context it
requests. This step does nothing but reorganise the code,
so that later the AP's chandef can be added to the request
in order to handle the EHT case described above.
Link: https://msgid.link/20240129194108.2e88e48bd2e9.I4256183debe975c5ed71621611206fdbb69ba330@changeid
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2024-01-29 19:34:40 +01:00
|
|
|
|
2018-05-28 15:47:38 +02:00
|
|
|
|
2013-07-08 16:55:53 +02:00
|
|
|
|
2011-06-23 09:00:11 -08:00
|
|
|
|
2013-07-08 16:55:53 +02:00
|
|
|
|
2010-08-28 19:37:51 +03:00
|
|
|
|
2014-06-12 22:24:31 +02:00
|
|
|
|
2021-11-29 15:32:45 +02:00
|
|
|
|
2011-11-08 13:04:41 +01:00
|
|
|
|
2012-11-29 13:00:10 +01:00
|
|
|
|
|
|
|
|
|
2014-02-05 15:21:13 +02:00
|
|
|
|
2024-01-29 20:19:33 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-01-05 20:16:44 +02:00
|
|
|
|
2009-02-15 12:44:28 +01:00
|
|
|
|
2010-01-05 20:16:44 +02:00
|
|
|
|
2009-02-15 12:44:28 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-11-18 18:42:05 +01:00
|
|
|
|
2011-11-08 13:04:41 +01:00
|
|
|
|
2010-11-11 08:50:18 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-07-08 16:55:53 +02:00
|
|
|
|
2009-02-15 12:44:28 +01:00
|
|
|
|
2016-04-12 15:56:15 +02:00
|
|
|
|
2009-02-15 12:44:28 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-03-29 22:14:20 +01:00
|
|
|
|
2023-08-29 12:17:44 +02:00
|
|
|
|
2017-04-27 12:45:38 +05:30
|
|
|
|
2013-07-08 16:55:53 +02:00
|
|
|
|
2017-04-27 12:45:38 +05:30
|
|
|
|
|
|
|
|
|
2013-07-08 16:55:53 +02:00
|
|
|
|
2009-02-15 12:44:28 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-04-02 21:21:21 -07:00
|
|
|
|
2009-02-15 12:44:28 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-04-02 21:21:21 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-03-29 22:14:20 +01:00
|
|
|
|
2013-07-08 16:55:53 +02:00
|
|
|
|
|
|
|
|
|
2009-02-15 12:44:28 +01:00
|
|
|
|
2012-04-02 21:21:21 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-02-15 12:44:28 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-04-14 10:09:24 +02:00
|
|
|
|
2024-06-18 19:25:56 +03:00
|
|
|
|
2009-08-20 20:02:20 +02:00
|
|
|
|
2024-06-26 09:15:59 +02:00
|
|
|
|
2024-05-15 13:53:19 +02:00
|
|
|
|
2024-06-26 09:15:59 +02:00
|
|
|
|
2024-05-15 13:53:19 +02:00
|
|
|
|
2009-08-20 20:02:20 +02:00
|
|
|
|
2010-11-30 08:59:23 +01:00
|
|
|
|
2009-08-20 20:02:20 +02:00
|
|
|
|
2023-08-28 13:59:49 +02:00
|
|
|
|
2009-08-20 20:02:20 +02:00
|
|
|
|
|
|
|
|
|
2023-08-28 13:59:34 +02:00
|
|
|
|
2024-06-18 19:25:56 +03:00
|
|
|
|
2009-08-20 20:02:20 +02:00
|
|
|
|
|
|
|
|
|
2015-12-08 16:04:38 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-08-28 13:59:39 +02:00
|
|
|
|
|
|
|
|
|
2015-12-08 16:04:38 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-04-30 14:19:04 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-08-28 14:00:03 +02:00
|
|
|
|
|
|
|
|
|
2014-04-30 14:19:04 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-06-10 20:19:37 +03:00
|
|
|
|
2023-06-04 12:11:28 +03:00
|
|
|
|
2014-04-30 14:19:04 +02:00
|
|
|
|
2015-12-08 16:04:38 +02:00
|
|
|
|
|
|
|
|
|
2014-04-30 14:19:04 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-02-28 10:55:30 +01:00
|
|
|
|
2022-05-30 18:35:23 +02:00
|
|
|
|
2022-06-17 22:36:37 +02:00
|
|
|
|
2013-02-28 10:55:30 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-08-28 14:00:03 +02:00
|
|
|
|
|
|
|
|
|
2022-06-17 22:36:37 +02:00
|
|
|
|
2023-08-28 14:00:03 +02:00
|
|
|
|
2013-02-28 10:55:30 +01:00
|
|
|
|
|
|
|
|
|
2022-07-03 18:04:15 +03:00
|
|
|
|
2013-02-28 10:55:30 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-12-08 16:04:39 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-08-28 14:00:01 +02:00
|
|
|
|
2023-08-28 14:00:03 +02:00
|
|
|
|
|
|
|
|
|
2015-12-08 16:04:39 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-03-26 12:14:35 +02:00
|
|
|
|
|
|
|
|
|
2016-09-20 17:31:20 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-02-21 20:03:00 -08:00
|
|
|
|
2016-09-20 17:31:20 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-03-26 12:14:34 +02:00
|
|
|
|
2016-09-20 17:31:20 +03:00
|
|
|
|
2026-03-26 12:14:34 +02:00
|
|
|
|
2016-09-20 17:31:20 +03:00
|
|
|
|
|
|
|
|
|
2026-03-26 12:14:34 +02:00
|
|
|
|
2016-09-20 17:31:20 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-03-26 12:14:35 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-03-26 12:14:37 +02:00
|
|
|
|
|
|
|
|
|
2026-03-26 12:14:38 +02:00
|
|
|
|
2026-03-26 12:14:35 +02:00
|
|
|
|
|
|
|
|
|
2026-03-26 12:14:37 +02:00
|
|
|
|
2026-03-26 12:14:35 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-09-20 17:31:20 +03:00
|
|
|
|
2026-03-26 12:14:37 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-03-26 12:14:38 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-03-26 12:14:39 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-03-26 12:14:38 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-09-20 17:31:20 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-05-04 16:45:11 +03:00
|
|
|
|
|
|
|
|
|
2023-06-04 12:11:13 +03:00
|
|
|
|
2023-05-04 16:45:11 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-04-14 10:09:24 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-07-26 17:24:39 +02:00
|
|
|
|
2009-04-14 10:09:24 +02:00
|
|
|
|
2011-07-14 20:29:42 +03:00
|
|
|
|
2013-01-10 23:55:33 +01:00
|
|
|
|
2013-12-08 21:48:57 +02:00
|
|
|
|
2014-11-19 11:55:49 +01:00
|
|
|
|
2013-12-08 21:48:57 +02:00
|
|
|
|
2015-07-08 15:41:47 +03:00
|
|
|
|
2022-03-08 17:23:24 +05:30
|
|
|
|
2013-01-10 23:55:33 +01:00
|
|
|
|
2023-08-28 14:00:03 +02:00
|
|
|
|
|
|
|
|
|
2014-12-14 11:05:53 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-01-11 00:28:01 +01:00
|
|
|
|
2015-07-08 15:41:47 +03:00
|
|
|
|
2009-11-19 14:29:39 +01:00
|
|
|
|
2009-04-14 10:09:24 +02:00
|
|
|
|
2011-05-04 15:37:29 +02:00
|
|
|
|
2015-07-08 15:41:47 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-05-04 15:37:29 +02:00
|
|
|
|
2013-08-07 20:11:55 +02:00
|
|
|
|
2011-05-04 15:37:29 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-07-08 15:41:47 +03:00
|
|
|
|
2011-05-04 15:37:29 +02:00
|
|
|
|
2013-01-10 23:55:33 +01:00
|
|
|
|
2015-07-08 15:41:47 +03:00
|
|
|
|
2011-05-04 15:37:29 +02:00
|
|
|
|
|
|
|
|
|
2011-07-14 16:48:54 +02:00
|
|
|
|
2015-10-25 10:59:35 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-10-25 10:59:36 +02:00
|
|
|
|
|
|
|
|
|
2011-07-14 16:48:54 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-07-08 15:41:47 +03:00
|
|
|
|
2014-04-30 14:19:04 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-11-19 17:35:39 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-04-30 14:19:04 +02:00
|
|
|
|
2011-07-14 16:48:54 +02:00
|
|
|
|
2009-04-14 10:09:24 +02:00
|
|
|
|
|
|
|
|
|
2011-12-30 16:34:25 +05:30
|
|
|
|
2025-06-15 13:53:09 +05:30
|
|
|
|
2011-12-30 16:34:25 +05:30
|
|
|
|
|
|
|
|
|
2025-06-15 13:53:12 +05:30
|
|
|
|
|
|
|
|
|
2025-09-03 11:39:04 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-06-15 13:53:12 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-12-30 16:34:25 +05:30
|
|
|
|
|
|
|
|
|
2025-06-15 13:53:09 +05:30
|
|
|
|
2011-12-30 16:34:25 +05:30
|
|
|
|
2011-07-14 16:48:54 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-04-14 10:09:24 +02:00
|
|
|
|
2021-11-12 13:51:44 +01:00
|
|
|
|
2024-06-12 12:23:51 +02:00
|
|
|
|
2013-03-27 23:20:27 +01:00
|
|
|
|
|
|
|
|
|
2012-04-03 14:35:57 +02:00
|
|
|
|
|
|
|
|
|
2014-03-24 00:51:43 +05:30
|
|
|
|
2012-04-03 14:35:57 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-04-14 10:09:24 +02:00
|
|
|
|
2024-10-09 10:25:48 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-03-26 12:14:37 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-04-14 10:09:24 +02:00
|
|
|
|
2015-03-01 09:10:04 +02:00
|
|
|
|
2011-11-03 14:41:13 +01:00
|
|
|
|
2015-03-01 09:10:04 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-10-09 10:25:48 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-03-26 12:14:37 +02:00
|
|
|
|
|
|
|
|
|
2015-03-01 09:10:04 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-10-09 10:25:48 +02:00
|
|
|
|
2015-03-01 09:10:04 +02:00
|
|
|
|
|
|
|
|
|
2009-04-14 10:09:24 +02:00
|
|
|
|
|
|
|
|
|
2012-07-26 17:24:39 +02:00
|
|
|
|
2024-01-29 19:34:38 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-07-26 17:24:39 +02:00
|
|
|
|
2024-01-29 19:34:38 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-11-19 22:19:08 +01:00
|
|
|
|
2009-04-14 10:09:24 +02:00
|
|
|
|
2025-06-15 13:53:09 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-04-14 10:09:24 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-05-04 16:45:05 +03:00
|
|
|
|
2023-06-04 12:11:13 +03:00
|
|
|
|
2023-05-04 16:45:05 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-06-17 22:36:37 +02:00
|
|
|
|
2023-05-04 16:45:05 +03:00
|
|
|
|
2010-05-05 09:44:02 +02:00
|
|
|
|
2009-12-23 13:15:31 +01:00
|
|
|
|
2009-04-14 10:09:24 +02:00
|
|
|
|
2010-05-05 09:44:02 +02:00
|
|
|
|
2023-06-08 16:36:08 +03:00
|
|
|
|
2023-05-04 16:45:05 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-03-20 09:14:05 +02:00
|
|
|
|
|
|
|
|
|
2022-06-17 22:36:37 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-02-28 09:48:11 +01:00
|
|
|
|
2023-05-04 16:45:05 +03:00
|
|
|
|
2022-06-17 22:36:37 +02:00
|
|
|
|
|
|
|
|
|
2023-05-04 16:45:05 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-05-30 18:35:23 +02:00
|
|
|
|
2015-12-08 16:04:39 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-03-26 12:14:38 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-02-06 13:17:12 +02:00
|
|
|
|
wifi: mac80211: move interface config to new struct
We'll use bss_conf for per-link configuration later, so
move out all the non-link-specific data out into a new
struct ieee80211_vif_cfg used in the vif.
Some adjustments were done with the following spatch:
@@
expression sdata;
struct ieee80211_vif *vifp;
identifier var = { assoc, ibss_joined, aid, arp_addr_list, arp_addr_cnt, ssid, ssid_len, s1g, ibss_creator };
@@
(
-sdata->vif.bss_conf.var
+sdata->vif.cfg.var
|
-vifp->bss_conf.var
+vifp->cfg.var
)
@bss_conf@
struct ieee80211_bss_conf *bss_conf;
identifier var = { assoc, ibss_joined, aid, arp_addr_list, arp_addr_cnt, ssid, ssid_len, s1g, ibss_creator };
@@
-bss_conf->var
+vif_cfg->var
(though more manual fixups were needed, e.g. replacing
"vif_cfg->" by "vif->cfg." in many files.)
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2022-05-10 17:05:04 +02:00
|
|
|
|
2019-02-06 13:17:12 +02:00
|
|
|
|
2020-07-07 15:45:48 -05:00
|
|
|
|
2015-12-08 16:04:39 +02:00
|
|
|
|
|
|
|
|
|
2020-07-07 15:45:48 -05:00
|
|
|
|
2015-12-08 16:04:39 +02:00
|
|
|
|
|
|
|
|
|
2022-06-24 15:40:11 +02:00
|
|
|
|
|
|
|
|
|
2015-12-08 16:04:39 +02:00
|
|
|
|
|
|
|
|
|
2010-05-05 09:44:02 +02:00
|
|
|
|
wifi: mac80211: move some future per-link data to bss_conf
To add MLD, reuse the bss_conf structure later for per-link
information, so move some things into it that are per link.
Most transformations were done with the following spatch:
@@
expression sdata;
identifier var = { chanctx_conf, mu_mimo_owner, csa_active, color_change_active, color_change_color };
@@
-sdata->vif.var
+sdata->vif.bss_conf.var
@@
struct ieee80211_vif *vif;
identifier var = { chanctx_conf, mu_mimo_owner, csa_active, color_change_active, color_change_color };
@@
-vif->var
+vif->bss_conf.var
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2022-05-10 13:26:44 +02:00
|
|
|
|
2015-12-08 16:04:31 +02:00
|
|
|
|
|
|
|
|
|
2023-06-08 16:36:08 +03:00
|
|
|
|
2023-05-04 16:45:05 +03:00
|
|
|
|
|
|
|
|
|
2009-04-14 10:09:24 +02:00
|
|
|
|
|
|
|
|
|
2023-06-08 16:36:08 +03:00
|
|
|
|
2023-05-04 16:45:05 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-12-12 10:12:24 +02:00
|
|
|
|
2023-05-04 16:45:05 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-12-12 10:12:24 +02:00
|
|
|
|
2023-05-04 16:45:05 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-04-26 10:58:47 +03:00
|
|
|
|
2023-05-04 16:45:05 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-04-28 11:25:38 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-05-04 16:45:05 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-05-05 09:44:02 +02:00
|
|
|
|
2014-11-03 10:33:18 +01:00
|
|
|
|
2014-11-03 10:33:19 +01:00
|
|
|
|
|
|
|
|
|
2014-11-03 10:33:18 +01:00
|
|
|
|
2009-04-14 10:09:24 +02:00
|
|
|
|
2010-05-05 09:44:02 +02:00
|
|
|
|
2020-07-07 15:45:48 -05:00
|
|
|
|
2009-04-14 10:09:24 +02:00
|
|
|
|
2023-05-04 16:45:11 +03:00
|
|
|
|
|
|
|
|
|
2023-06-08 16:36:08 +03:00
|
|
|
|
2023-05-04 16:45:11 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-11-22 19:33:18 +02:00
|
|
|
|
2018-10-03 20:19:20 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-10-19 15:44:42 +02:00
|
|
|
|
2011-11-22 19:33:18 +02:00
|
|
|
|
|
|
|
|
|
2023-06-08 16:36:08 +03:00
|
|
|
|
2023-05-04 16:45:11 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-05-16 15:00:15 +02:00
|
|
|
|
2022-06-29 12:22:24 +03:00
|
|
|
|
|
|
|
|
|
2012-10-19 15:44:42 +02:00
|
|
|
|
2020-07-07 15:45:48 -05:00
|
|
|
|
2009-04-14 10:09:24 +02:00
|
|
|
|
2012-12-14 14:17:26 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-04-14 10:09:24 +02:00
|
|
|
|
2016-09-20 17:31:20 +03:00
|
|
|
|
wifi: mac80211: don't call ieee80211_handle_reconfig_failure when not needed
In case reconfiguration of NAN fails, we call
ieee80211_handle_reconfig_failure, that marks all interfaces as not in
the driver.
Then, at the error path of the reconfig, cfg80211_shutdown_all_interfaces
is called to destroy all the interfaces.
If we have any other interface but the NAN one, for example a BSS
station, then when its state (links, stations) will be removed, we
won't tell the driver about this, because we will think that the
interfaces are not in the driver, and then drivers might remain with
dangling pointers to objects like stations and links (at least for
iwlwifi this is the case).
ieee80211_handle_reconfig_failure is meant to be called after we cleaned
up the state in the driver, there is no reason to call it for NAN
reconfiguration failure.
Fix the code to just warn in such a case, as we do in other error paths
in reconfig where it is too complicated to rewind.
Signed-off-by: Miri Korenblit <miriam.rachel.korenblit@intel.com>
Link: https://patch.msgid.link/20260513182548.6a25f3a0a6ec.I83d1f2a7eed20200a78a62757c6b193e3bab892b@changeid
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2026-05-13 18:26:56 +03:00
|
|
|
|
2016-09-20 17:31:20 +03:00
|
|
|
|
2026-03-18 14:39:17 +02:00
|
|
|
|
2009-04-14 10:09:24 +02:00
|
|
|
|
|
|
|
|
|
2012-06-16 00:19:54 +02:00
|
|
|
|
2026-04-20 14:38:46 +05:30
|
|
|
|
2014-04-26 09:43:41 +08:00
|
|
|
|
2012-06-18 20:07:15 +02:00
|
|
|
|
2009-04-14 10:09:24 +02:00
|
|
|
|
2010-08-12 15:38:38 +02:00
|
|
|
|
2010-09-16 14:58:23 +02:00
|
|
|
|
|
|
|
|
|
2020-11-09 10:57:46 +01:00
|
|
|
|
2009-04-14 10:09:24 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-10-14 18:02:43 +02:00
|
|
|
|
2011-11-09 12:29:06 +02:00
|
|
|
|
2012-01-26 13:36:05 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-11-08 14:06:28 +01:00
|
|
|
|
|
|
|
|
|
2012-01-26 13:36:05 +02:00
|
|
|
|
2015-09-24 16:14:55 +02:00
|
|
|
|
2012-01-26 13:36:05 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-06-03 23:31:56 +03:00
|
|
|
|
2022-09-02 16:12:51 +02:00
|
|
|
|
|
|
|
|
|
2012-06-03 23:31:56 +03:00
|
|
|
|
|
|
|
|
|
2022-09-02 16:12:51 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-06-03 23:31:56 +03:00
|
|
|
|
|
|
|
|
|
2012-05-29 02:00:22 -07:00
|
|
|
|
2015-05-13 09:16:48 +00:00
|
|
|
|
2019-08-30 14:24:49 +03:00
|
|
|
|
2012-05-29 02:00:22 -07:00
|
|
|
|
2024-03-20 09:14:05 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-04-15 11:27:13 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-03-20 09:14:05 +02:00
|
|
|
|
|
|
|
|
|
2015-10-25 10:59:33 +02:00
|
|
|
|
|
|
|
|
|
2023-08-28 14:00:05 +02:00
|
|
|
|
2015-10-25 10:59:33 +02:00
|
|
|
|
2023-08-28 14:00:05 +02:00
|
|
|
|
2015-10-25 10:59:33 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-12-16 15:45:45 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-10-25 10:59:33 +02:00
|
|
|
|
2015-12-16 15:45:45 +02:00
|
|
|
|
2015-10-25 10:59:33 +02:00
|
|
|
|
|
|
|
|
|
2021-01-22 16:19:43 +01:00
|
|
|
|
2015-10-25 10:59:33 +02:00
|
|
|
|
2012-07-02 15:08:25 +03:00
|
|
|
|
2010-06-10 10:21:29 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-06-02 21:39:54 +02:00
|
|
|
|
2010-06-10 10:21:29 +02:00
|
|
|
|
2015-09-21 15:50:26 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-09-29 16:04:36 +02:00
|
|
|
|
2010-02-03 09:28:55 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-11-29 15:32:40 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-10-29 11:51:08 +02:00
|
|
|
|
2022-03-08 17:23:24 +05:30
|
|
|
|
2017-10-29 11:51:08 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-05-23 12:03:52 +02:00
|
|
|
|
2019-05-29 15:25:30 +03:00
|
|
|
|
|
|
|
|
|
2025-03-06 12:37:56 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-10-29 11:51:08 +02:00
|
|
|
|
|
|
|
|
|
2013-02-13 12:25:28 +01:00
|
|
|
|
2014-06-13 16:30:05 +03:00
|
|
|
|
|
|
|
|
|
2009-04-14 10:09:24 +02:00
|
|
|
|
2022-03-08 17:23:24 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-11-10 14:18:20 +02:00
|
|
|
|
2025-07-09 23:34:56 +03:00
|
|
|
|
|
|
|
|
|
2025-11-10 14:18:20 +02:00
|
|
|
|
2025-07-09 23:34:56 +03:00
|
|
|
|
2015-07-08 15:41:47 +03:00
|
|
|
|
2009-05-17 11:40:42 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-11-19 14:29:39 +01:00
|
|
|
|
2009-05-17 11:40:42 +02:00
|
|
|
|
2009-11-19 14:29:39 +01:00
|
|
|
|
|
|
|
|
|
2009-05-17 11:40:42 +02:00
|
|
|
|
2015-12-08 16:04:38 +02:00
|
|
|
|
2015-01-24 10:30:02 +02:00
|
|
|
|
2014-12-14 11:05:53 +02:00
|
|
|
|
2014-11-04 11:43:54 +02:00
|
|
|
|
|
|
|
|
|
2013-04-29 14:57:44 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-04-01 13:52:48 +02:00
|
|
|
|
2009-05-17 11:40:42 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-12-08 21:48:57 +02:00
|
|
|
|
2009-04-14 10:09:24 +02:00
|
|
|
|
|
|
|
|
|
2009-07-29 20:08:07 -04:00
|
|
|
|
2022-03-08 17:23:24 +05:30
|
|
|
|
2011-07-12 12:30:59 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-08-28 14:00:02 +02:00
|
|
|
|
|
|
|
|
|
2022-03-08 17:23:24 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-07-12 12:30:59 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-03-08 17:23:24 +05:30
|
|
|
|
2011-07-12 12:30:59 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-03-08 17:23:24 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-07-12 12:30:59 +02:00
|
|
|
|
|
|
|
|
|
2022-05-30 23:45:04 +02:00
|
|
|
|
2022-06-17 22:36:37 +02:00
|
|
|
|
2009-12-01 13:37:02 +01:00
|
|
|
|
2012-09-11 14:34:12 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-12-01 13:37:02 +01:00
|
|
|
|
2023-08-28 14:00:03 +02:00
|
|
|
|
2009-12-01 13:37:02 +01:00
|
|
|
|
2022-06-17 22:36:37 +02:00
|
|
|
|
2023-08-28 14:00:03 +02:00
|
|
|
|
2009-12-01 13:37:02 +01:00
|
|
|
|
2015-10-25 10:59:40 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-08-28 14:00:03 +02:00
|
|
|
|
2009-12-01 13:37:02 +01:00
|
|
|
|
2012-09-11 14:34:12 +02:00
|
|
|
|
|
|
|
|
|
2009-12-01 13:37:02 +01:00
|
|
|
|
2009-12-23 13:15:38 +01:00
|
|
|
|
2022-06-22 16:15:56 +03:00
|
|
|
|
|
|
|
|
|
2013-11-11 20:14:01 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-06-22 16:15:56 +03:00
|
|
|
|
2013-11-11 20:14:01 +02:00
|
|
|
|
2023-08-28 14:00:03 +02:00
|
|
|
|
2013-11-11 20:14:01 +02:00
|
|
|
|
2022-06-22 16:15:56 +03:00
|
|
|
|
|
|
|
|
|
2013-11-11 20:14:01 +02:00
|
|
|
|
2022-06-22 16:15:56 +03:00
|
|
|
|
|
|
|
|
|
2013-11-11 20:14:01 +02:00
|
|
|
|
2022-06-22 16:15:56 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-08-28 14:00:03 +02:00
|
|
|
|
2022-06-22 16:15:56 +03:00
|
|
|
|
2023-08-28 14:00:03 +02:00
|
|
|
|
2022-06-22 16:15:56 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-09-02 16:12:42 +02:00
|
|
|
|
2023-08-28 14:00:03 +02:00
|
|
|
|
2022-06-22 16:15:56 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-11-05 16:03:44 +01:00
|
|
|
|
2022-06-22 16:15:56 +03:00
|
|
|
|
2013-11-11 20:14:01 +02:00
|
|
|
|
|
|
|
|
|
2009-12-23 13:15:38 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-07-08 08:46:22 -07:00
|
|
|
|
2011-11-18 11:32:00 -08:00
|
|
|
|
2011-10-26 14:47:26 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-11-18 11:32:00 -08:00
|
|
|
|
|
|
|
|
|
2011-10-26 14:47:26 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-11-18 11:32:00 -08:00
|
|
|
|
|
|
|
|
|
2011-10-26 14:47:26 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-07-02 11:25:12 +00:00
|
|
|
|
2012-12-07 12:45:06 +01:00
|
|
|
|
2012-07-02 11:25:12 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-10-10 11:25:40 +00:00
|
|
|
|
|
|
|
|
|
2012-07-02 11:25:12 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-01-29 20:19:35 +01:00
|
|
|
|
2024-01-29 20:19:27 +01:00
|
|
|
|
2019-07-24 18:33:56 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-01-29 20:19:27 +01:00
|
|
|
|
2019-07-24 18:33:56 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-01-29 20:19:28 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-01-29 20:19:29 +01:00
|
|
|
|
|
|
|
|
|
2024-01-29 20:19:28 +01:00
|
|
|
|
|
|
|
|
|
2024-01-29 20:19:29 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-01-29 20:19:28 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-01-29 20:19:29 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-01-29 20:19:28 +01:00
|
|
|
|
2024-01-29 20:19:29 +01:00
|
|
|
|
2024-01-29 20:19:28 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-01-29 20:19:29 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-01-29 20:19:28 +01:00
|
|
|
|
|
|
|
|
|
2024-01-29 20:19:35 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-06-09 09:14:44 +03:00
|
|
|
|
2024-01-29 20:19:35 +01:00
|
|
|
|
2022-02-02 10:49:34 +02:00
|
|
|
|
2024-01-29 20:19:35 +01:00
|
|
|
|
2018-06-09 09:14:44 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-01-29 19:34:36 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-01-29 20:19:35 +01:00
|
|
|
|
2018-06-09 09:14:44 +03:00
|
|
|
|
2024-01-29 20:19:35 +01:00
|
|
|
|
2018-06-09 09:14:44 +03:00
|
|
|
|
2022-02-02 10:49:34 +02:00
|
|
|
|
2024-01-29 20:19:28 +01:00
|
|
|
|
2022-02-02 10:49:34 +02:00
|
|
|
|
|
|
|
|
|
2018-06-09 09:14:44 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-01-29 20:19:35 +01:00
|
|
|
|
|
|
|
|
|
2018-06-09 09:14:44 +03:00
|
|
|
|
2024-01-29 20:19:35 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-06-09 09:14:44 +03:00
|
|
|
|
|
|
|
|
|
2024-01-29 20:19:35 +01:00
|
|
|
|
2018-06-09 09:14:44 +03:00
|
|
|
|
2024-01-29 20:19:35 +01:00
|
|
|
|
2018-06-09 09:14:44 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-01-29 20:19:35 +01:00
|
|
|
|
2018-06-09 09:14:44 +03:00
|
|
|
|
|
|
|
|
|
2024-01-29 20:19:35 +01:00
|
|
|
|
|
|
|
|
|
2018-06-09 09:14:44 +03:00
|
|
|
|
|
|
|
|
|
2026-07-15 21:03:33 +03:00
|
|
|
|
|
|
|
|
|
2025-06-09 21:35:26 +03:00
|
|
|
|
2026-07-15 21:03:33 +03:00
|
|
|
|
2025-06-09 21:35:26 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-07-15 21:03:33 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-06-09 21:35:26 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-01-29 20:19:33 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-05-28 21:34:32 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-01-29 20:19:33 +01:00
|
|
|
|
2020-05-28 21:34:32 +02:00
|
|
|
|
2021-06-23 13:05:47 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-01-29 20:19:33 +01:00
|
|
|
|
2020-05-28 21:34:32 +02:00
|
|
|
|
2021-06-23 13:05:47 +02:00
|
|
|
|
|
|
|
|
|
2020-05-28 21:34:32 +02:00
|
|
|
|
2021-06-23 13:05:47 +02:00
|
|
|
|
2024-01-29 20:19:33 +01:00
|
|
|
|
2020-05-28 21:34:32 +02:00
|
|
|
|
2020-07-01 19:20:24 -07:00
|
|
|
|
|
|
|
|
|
2024-01-29 20:19:33 +01:00
|
|
|
|
2020-07-01 19:20:24 -07:00
|
|
|
|
2024-01-29 20:19:33 +01:00
|
|
|
|
|
|
|
|
|
2020-05-28 21:34:32 +02:00
|
|
|
|
2022-08-25 20:57:32 +02:00
|
|
|
|
2020-05-28 21:34:32 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-07-07 15:45:48 -05:00
|
|
|
|
2020-05-28 21:34:32 +02:00
|
|
|
|
2024-01-29 20:19:33 +01:00
|
|
|
|
|
|
|
|
|
2020-05-28 21:34:32 +02:00
|
|
|
|
|
|
|
|
|
2024-01-29 20:19:33 +01:00
|
|
|
|
|
|
|
|
|
2020-05-28 21:34:32 +02:00
|
|
|
|
|
|
|
|
|
2024-01-29 20:19:33 +01:00
|
|
|
|
|
|
|
|
|
2020-05-28 21:34:32 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-01-29 20:19:33 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-05-28 21:34:32 +02:00
|
|
|
|
|
|
|
|
|
2012-03-15 19:45:16 +01:00
|
|
|
|
2012-11-09 11:39:59 +01:00
|
|
|
|
2015-10-25 10:59:34 +02:00
|
|
|
|
2011-10-26 14:47:26 -07:00
|
|
|
|
2012-03-15 19:45:16 +01:00
|
|
|
|
2011-10-26 14:47:26 -07:00
|
|
|
|
2012-03-15 19:45:16 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-11-09 11:39:59 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-10-26 14:47:26 -07:00
|
|
|
|
2022-02-14 17:30:00 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-10-26 14:47:26 -07:00
|
|
|
|
2012-03-15 19:45:16 +01:00
|
|
|
|
2011-10-26 14:47:26 -07:00
|
|
|
|
|
|
|
|
|
2012-04-18 19:24:14 -07:00
|
|
|
|
2012-11-09 11:39:59 +01:00
|
|
|
|
|
|
|
|
|
2012-03-15 19:45:16 +01:00
|
|
|
|
2011-11-30 16:56:33 +01:00
|
|
|
|
2015-10-25 10:59:34 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-04-30 14:20:29 -07:00
|
|
|
|
2012-03-15 19:45:16 +01:00
|
|
|
|
2011-10-26 14:47:26 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-03-15 19:45:16 +01:00
|
|
|
|
|
|
|
|
|
2011-10-26 14:47:26 -07:00
|
|
|
|
2012-03-15 19:45:16 +01:00
|
|
|
|
2011-10-26 14:47:26 -07:00
|
|
|
|
|
|
|
|
|
2017-05-23 17:00:42 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-02-14 17:30:00 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-05-23 17:00:42 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-03-01 09:10:02 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-02-15 15:02:06 +01:00
|
|
|
|
2015-03-01 09:10:02 +02:00
|
|
|
|
|
|
|
|
|
2017-02-15 15:02:06 +01:00
|
|
|
|
2015-03-01 09:10:02 +02:00
|
|
|
|
2015-09-04 10:58:05 +08:00
|
|
|
|
2017-02-15 15:02:06 +01:00
|
|
|
|
2015-03-01 09:10:02 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-02-01 11:40:55 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-02-15 15:02:06 +01:00
|
|
|
|
2016-02-01 11:40:55 +02:00
|
|
|
|
2017-02-15 15:02:06 +01:00
|
|
|
|
2016-02-01 11:40:55 +02:00
|
|
|
|
2017-02-15 15:02:06 +01:00
|
|
|
|
2015-03-01 09:10:02 +02:00
|
|
|
|
|
|
|
|
|
2016-02-01 11:40:55 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-03-01 09:10:02 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-02-14 17:30:00 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-03-01 09:10:02 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-09-10 13:40:03 -07:00
|
|
|
|
2019-07-24 18:33:56 +02:00
|
|
|
|
|
|
|
|
|
2020-05-28 21:34:33 +02:00
|
|
|
|
2024-11-19 09:57:59 +05:30
|
|
|
|
2019-07-24 18:33:56 +02:00
|
|
|
|
2020-05-28 21:34:33 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-07-24 18:33:56 +02:00
|
|
|
|
|
|
|
|
|
2020-05-28 21:34:33 +02:00
|
|
|
|
2019-07-24 18:33:56 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-05-28 21:34:33 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-07-24 18:33:56 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-05-28 21:34:33 +02:00
|
|
|
|
2019-07-24 18:33:56 +02:00
|
|
|
|
2020-05-28 21:34:33 +02:00
|
|
|
|
|
|
|
|
|
2019-07-24 18:33:56 +02:00
|
|
|
|
2024-11-19 09:57:59 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-05-28 21:34:33 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-11-19 09:57:59 +05:30
|
|
|
|
2020-05-28 21:34:33 +02:00
|
|
|
|
2024-11-19 09:57:59 +05:30
|
|
|
|
|
|
|
|
|
2020-05-28 21:34:33 +02:00
|
|
|
|
2024-11-19 09:57:59 +05:30
|
|
|
|
2020-05-28 21:34:33 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-11-19 09:57:59 +05:30
|
|
|
|
2022-02-14 17:30:00 +01:00
|
|
|
|
2024-11-19 09:57:59 +05:30
|
|
|
|
|
|
|
|
|
2022-02-14 17:30:00 +01:00
|
|
|
|
2024-11-19 09:57:59 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-05-28 21:34:33 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-11-19 09:57:59 +05:30
|
|
|
|
2020-05-28 21:34:33 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-07-24 18:33:56 +02:00
|
|
|
|
|
|
|
|
|
2024-09-10 13:40:03 -07:00
|
|
|
|
2023-03-28 01:07:42 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-12-18 15:08:34 +01:00
|
|
|
|
|
|
|
|
|
2011-10-26 14:47:26 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-12-18 15:08:34 +01:00
|
|
|
|
|
|
|
|
|
2011-10-26 14:47:26 -07:00
|
|
|
|
2012-03-15 19:45:16 +01:00
|
|
|
|
2011-10-26 14:47:26 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-12-18 15:08:34 +01:00
|
|
|
|
2011-10-26 14:47:26 -07:00
|
|
|
|
|
|
|
|
|
2015-12-18 15:08:34 +01:00
|
|
|
|
|
|
|
|
|
2011-10-26 14:47:26 -07:00
|
|
|
|
|
|
|
|
|
2020-05-28 21:34:35 +02:00
|
|
|
|
2018-08-31 11:31:18 +03:00
|
|
|
|
|
|
|
|
|
2015-12-18 15:08:34 +01:00
|
|
|
|
2015-03-20 06:37:01 +01:00
|
|
|
|
2015-12-18 15:08:34 +01:00
|
|
|
|
2018-08-31 11:31:18 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-02-10 15:07:28 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-05-28 21:34:35 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-03-20 06:37:01 +01:00
|
|
|
|
2018-08-31 11:31:18 +03:00
|
|
|
|
2015-12-18 15:08:34 +01:00
|
|
|
|
|
|
|
|
|
2020-02-10 15:07:28 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-08-31 11:31:18 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-05-28 21:34:35 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-04-15 14:51:57 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-05-28 21:34:35 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-07-07 15:45:48 -05:00
|
|
|
|
2020-05-28 21:34:35 +02:00
|
|
|
|
|
|
|
|
|
2018-08-31 11:31:18 +03:00
|
|
|
|
2020-05-28 21:34:35 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-08-31 11:31:18 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-03-20 06:37:01 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-08-31 11:31:18 +03:00
|
|
|
|
2015-03-20 06:37:01 +01:00
|
|
|
|
|
|
|
|
|
2015-12-18 15:08:34 +01:00
|
|
|
|
2018-08-31 11:31:18 +03:00
|
|
|
|
2016-02-01 11:40:55 +02:00
|
|
|
|
2018-08-31 11:31:18 +03:00
|
|
|
|
2016-02-01 11:40:55 +02:00
|
|
|
|
|
|
|
|
|
2018-08-31 11:31:18 +03:00
|
|
|
|
2020-02-10 15:07:28 +02:00
|
|
|
|
2016-02-01 11:40:55 +02:00
|
|
|
|
2018-08-31 11:31:18 +03:00
|
|
|
|
2020-02-10 15:07:28 +02:00
|
|
|
|
2016-02-01 11:40:55 +02:00
|
|
|
|
2018-08-31 11:31:18 +03:00
|
|
|
|
2016-02-01 11:40:55 +02:00
|
|
|
|
|
|
|
|
|
2015-03-20 06:37:01 +01:00
|
|
|
|
|
|
|
|
|
2018-08-31 11:31:18 +03:00
|
|
|
|
2015-12-18 15:08:34 +01:00
|
|
|
|
2018-08-31 11:31:18 +03:00
|
|
|
|
2015-03-20 06:37:01 +01:00
|
|
|
|
|
|
|
|
|
2018-08-31 11:31:18 +03:00
|
|
|
|
2015-12-18 15:08:34 +01:00
|
|
|
|
2018-08-31 11:31:18 +03:00
|
|
|
|
|
|
|
|
|
2015-03-20 06:37:01 +01:00
|
|
|
|
|
|
|
|
|
2015-12-18 15:08:34 +01:00
|
|
|
|
2015-03-20 06:37:01 +01:00
|
|
|
|
|
|
|
|
|
2015-12-18 15:08:34 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-03-20 06:37:01 +01:00
|
|
|
|
|
|
|
|
|
2023-09-20 21:25:12 +03:00
|
|
|
|
2022-04-27 18:02:10 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-01-29 19:34:37 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-04-27 18:02:10 +03:00
|
|
|
|
|
|
|
|
|
2024-01-29 19:34:37 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-04-27 18:02:10 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-01-29 19:34:37 +01:00
|
|
|
|
2020-05-28 21:34:36 +02:00
|
|
|
|
2022-02-14 17:30:00 +01:00
|
|
|
|
2020-05-28 21:34:36 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-01-29 19:34:37 +01:00
|
|
|
|
2020-05-28 21:34:36 +02:00
|
|
|
|
2022-02-14 17:30:00 +01:00
|
|
|
|
2020-05-28 21:34:36 +02:00
|
|
|
|
2024-01-11 18:17:45 +02:00
|
|
|
|
2020-05-28 21:34:36 +02:00
|
|
|
|
|
|
|
|
|
2022-02-14 17:30:00 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-05-28 21:34:36 +02:00
|
|
|
|
|
|
|
|
|
2024-01-29 19:34:37 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-05-28 21:34:36 +02:00
|
|
|
|
2022-04-27 18:02:10 +03:00
|
|
|
|
|
|
|
|
|
2022-02-14 17:30:00 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-01-29 19:34:37 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-05-28 21:34:36 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-02-14 17:30:00 +01:00
|
|
|
|
|
|
|
|
|
2020-09-18 13:53:04 +02:00
|
|
|
|
|
|
|
|
|
2022-02-14 17:30:00 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-01-29 19:34:37 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-02-14 17:30:00 +01:00
|
|
|
|
|
|
|
|
|
2023-09-20 21:25:12 +03:00
|
|
|
|
|
|
|
|
|
2024-03-12 12:59:46 +08:00
|
|
|
|
|
|
|
|
|
2020-05-28 21:34:36 +02:00
|
|
|
|
|
|
|
|
|
2024-01-29 19:34:37 +01:00
|
|
|
|
2020-05-28 21:34:36 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-11-23 16:45:52 +08:00
|
|
|
|
2020-09-21 19:28:15 -07:00
|
|
|
|
|
|
|
|
|
2025-09-18 15:19:12 +10:00
|
|
|
|
|
|
|
|
|
2020-09-21 19:28:15 -07:00
|
|
|
|
|
|
|
|
|
2025-09-18 15:19:12 +10:00
|
|
|
|
2020-09-21 19:28:15 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-09-18 15:19:12 +10:00
|
|
|
|
2020-09-21 19:28:15 -07:00
|
|
|
|
2025-09-18 15:19:12 +10:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-05-28 21:34:36 +02:00
|
|
|
|
|
|
|
|
|
2024-01-29 20:19:32 +01:00
|
|
|
|
|
|
|
|
|
2025-03-29 22:14:20 +01:00
|
|
|
|
2024-01-29 20:19:32 +01:00
|
|
|
|
2011-09-28 14:12:51 +03:00
|
|
|
|
2024-01-29 20:19:32 +01:00
|
|
|
|
2011-09-28 14:12:51 +03:00
|
|
|
|
2013-07-08 16:55:53 +02:00
|
|
|
|
|
|
|
|
|
2024-01-29 20:19:32 +01:00
|
|
|
|
|
|
|
|
|
2013-07-08 16:55:53 +02:00
|
|
|
|
|
|
|
|
|
2024-01-29 20:19:32 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-09-28 14:12:51 +03:00
|
|
|
|
|
|
|
|
|
2024-01-29 20:19:32 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-09-28 14:12:51 +03:00
|
|
|
|
2024-01-29 20:19:32 +01:00
|
|
|
|
2013-07-08 16:55:53 +02:00
|
|
|
|
|
|
|
|
|
2024-01-29 20:19:32 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-09-28 14:12:51 +03:00
|
|
|
|
2024-01-29 20:19:32 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-09-28 14:12:51 +03:00
|
|
|
|
2024-01-29 20:19:32 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-09-28 14:12:51 +03:00
|
|
|
|
|
|
|
|
|
2012-04-13 12:02:57 -07:00
|
|
|
|
wifi: mac80211: add support towards MLO handling of station statistics
Currently, in supporting API's to fill sinfo structure from sta
structure, is mapped to fill the fields from sta->deflink. However,
for multi-link (ML) station, sinfo structure should be filled from
corresponding link_id.
Therefore, add link_id as an additional argument in supporting API's
for filling sinfo structure correctly. Link_id is set to -1 for non-ML
station and corresponding link_id for ML stations. In supporting API's
for filling sinfo structure, check for link_id, if link_id < 0, fill
the sinfo structure from sta->deflink, otherwise fill from
sta->link[link_id].
Current, changes are done at the deflink level i.e, pass -1 as link_id.
Actual link_id will be added in subsequent patches to support
station statistics for MLO.
Signed-off-by: Sarika Sharma <quic_sarishar@quicinc.com>
Link: https://patch.msgid.link/20250528054420.3050133-2-quic_sarishar@quicinc.com
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2025-05-28 11:14:11 +05:30
|
|
|
|
2012-04-13 12:02:57 -07:00
|
|
|
|
|
|
|
|
|
wifi: mac80211: add support towards MLO handling of station statistics
Currently, in supporting API's to fill sinfo structure from sta
structure, is mapped to fill the fields from sta->deflink. However,
for multi-link (ML) station, sinfo structure should be filled from
corresponding link_id.
Therefore, add link_id as an additional argument in supporting API's
for filling sinfo structure correctly. Link_id is set to -1 for non-ML
station and corresponding link_id for ML stations. In supporting API's
for filling sinfo structure, check for link_id, if link_id < 0, fill
the sinfo structure from sta->deflink, otherwise fill from
sta->link[link_id].
Current, changes are done at the deflink level i.e, pass -1 as link_id.
Actual link_id will be added in subsequent patches to support
station statistics for MLO.
Signed-off-by: Sarika Sharma <quic_sarishar@quicinc.com>
Link: https://patch.msgid.link/20250528054420.3050133-2-quic_sarishar@quicinc.com
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2025-05-28 11:14:11 +05:30
|
|
|
|
2012-04-13 12:02:57 -07:00
|
|
|
|
2022-05-16 15:00:15 +02:00
|
|
|
|
2012-04-23 09:30:32 -07:00
|
|
|
|
2022-05-16 15:00:15 +02:00
|
|
|
|
wifi: mac80211: add support towards MLO handling of station statistics
Currently, in supporting API's to fill sinfo structure from sta
structure, is mapped to fill the fields from sta->deflink. However,
for multi-link (ML) station, sinfo structure should be filled from
corresponding link_id.
Therefore, add link_id as an additional argument in supporting API's
for filling sinfo structure correctly. Link_id is set to -1 for non-ML
station and corresponding link_id for ML stations. In supporting API's
for filling sinfo structure, check for link_id, if link_id < 0, fill
the sinfo structure from sta->deflink, otherwise fill from
sta->link[link_id].
Current, changes are done at the deflink level i.e, pass -1 as link_id.
Actual link_id will be added in subsequent patches to support
station statistics for MLO.
Signed-off-by: Sarika Sharma <quic_sarishar@quicinc.com>
Link: https://patch.msgid.link/20250528054420.3050133-2-quic_sarishar@quicinc.com
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2025-05-28 11:14:11 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-04-13 12:02:57 -07:00
|
|
|
|
2012-04-20 11:57:00 -07:00
|
|
|
|
2012-09-11 14:34:12 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-11-13 10:46:27 -08:00
|
|
|
|
2026-03-26 12:14:33 +02:00
|
|
|
|
2012-11-13 10:46:27 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-12-20 13:41:39 +02:00
|
|
|
|
2012-11-13 10:46:27 -08:00
|
|
|
|
|
|
|
|
|
2020-12-06 14:54:45 +02:00
|
|
|
|
2012-11-13 10:46:27 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-12-20 13:41:39 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-11-13 10:46:27 -08:00
|
|
|
|
|
|
|
|
|
2018-04-20 13:49:21 +03:00
|
|
|
|
|
|
|
|
|
2012-11-13 10:46:27 -08:00
|
|
|
|
2017-04-26 12:14:59 +02:00
|
|
|
|
2023-01-09 13:07:21 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-12-20 13:41:39 +02:00
|
|
|
|
2023-01-09 13:07:21 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-12-06 14:54:45 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-12-20 13:41:39 +02:00
|
|
|
|
2020-12-06 14:54:45 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-04-26 12:14:59 +02:00
|
|
|
|
2012-11-13 10:46:27 -08:00
|
|
|
|
|
|
|
|
|
2017-04-26 11:13:00 +02:00
|
|
|
|
2012-11-13 10:46:27 -08:00
|
|
|
|
2020-12-06 14:54:45 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-12-20 13:41:39 +02:00
|
|
|
|
2020-12-06 14:54:45 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-04-26 12:14:59 +02:00
|
|
|
|
|
|
|
|
|
2012-11-09 15:07:02 +01:00
|
|
|
|
|
|
|
|
|
2017-04-26 13:51:41 +02:00
|
|
|
|
2017-04-26 11:13:00 +02:00
|
|
|
|
2012-11-09 15:07:02 +01:00
|
|
|
|
2020-12-06 14:54:45 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-12-20 13:41:39 +02:00
|
|
|
|
2020-12-06 14:54:45 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-04-26 12:14:59 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-07-07 15:45:48 -05:00
|
|
|
|
2017-04-26 12:14:59 +02:00
|
|
|
|
2012-11-13 10:46:27 -08:00
|
|
|
|
|
|
|
|
|
2026-03-26 12:14:33 +02:00
|
|
|
|
2023-08-29 12:17:44 +02:00
|
|
|
|
2016-01-25 15:46:34 +02:00
|
|
|
|
2023-12-20 13:41:39 +02:00
|
|
|
|
2016-04-12 15:56:15 +02:00
|
|
|
|
2023-08-29 12:17:44 +02:00
|
|
|
|
2016-01-25 15:46:34 +02:00
|
|
|
|
2017-04-26 11:13:00 +02:00
|
|
|
|
2016-01-25 15:46:34 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-04-26 12:14:59 +02:00
|
|
|
|
|
|
|
|
|
2012-11-13 10:46:27 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-10-11 15:47:06 +02:00
|
|
|
|
2016-02-24 11:49:45 +02:00
|
|
|
|
|
|
|
|
|
2017-04-26 13:51:41 +02:00
|
|
|
|
2013-10-11 15:47:06 +02:00
|
|
|
|
2012-11-13 10:46:27 -08:00
|
|
|
|
|
|
|
|
|
2023-12-20 13:41:39 +02:00
|
|
|
|
2012-11-13 10:46:27 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-03-26 12:14:33 +02:00
|
|
|
|
2013-02-08 18:16:20 +01:00
|
|
|
|
wifi: mac80211: handle ieee80211_radar_detected() for MLO
Currently DFS works under assumption there could be only one channel
context in the hardware. Hence, drivers just calls the function
ieee80211_radar_detected() passing the hardware structure. However, with
MLO, this obviously will not work since number of channel contexts will be
more than one and hence drivers would need to pass the channel information
as well on which the radar is detected.
Also, when radar is detected in one of the links, other link's CAC should
not be cancelled.
Hence, in order to support DFS with MLO, do the following changes -
* Add channel context conf pointer as an argument to the function
ieee80211_radar_detected(). During MLO, drivers would have to pass on
which channel context conf radar is detected. Otherwise, drivers could
just pass NULL.
* ieee80211_radar_detected() will iterate over all channel contexts
present and
* if channel context conf is passed, only mark that as radar
detected
* if NULL is passed, then mark all channel contexts as radar
detected
* Then as usual, schedule the radar detected work.
* In the worker, go over all the contexts again and for all such context
which is marked with radar detected, cancel the ongoing CAC by calling
ieee80211_dfs_cac_cancel() and then notify cfg80211 via
cfg80211_radar_event().
* To cancel the CAC, pass the channel context as well where radar is
detected to ieee80211_dfs_cac_cancel(). This ensures that CAC is
canceled only on the links using the provided context, leaving other
links unaffected.
This would also help in scenarios where there is split phy 5 GHz radio,
which is capable of DFS channels in both lower and upper band. In this
case, simultaneous radars can be detected.
Signed-off-by: Aditya Kumar Singh <quic_adisi@quicinc.com>
Link: https://patch.msgid.link/20240906064426.2101315-9-quic_adisi@quicinc.com
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2024-09-06 12:14:26 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-02-08 18:16:20 +01:00
|
|
|
|
|
|
|
|
|
2013-11-06 13:55:51 +01:00
|
|
|
|
2024-09-06 12:14:24 +05:30
|
|
|
|
wifi: mac80211: handle ieee80211_radar_detected() for MLO
Currently DFS works under assumption there could be only one channel
context in the hardware. Hence, drivers just calls the function
ieee80211_radar_detected() passing the hardware structure. However, with
MLO, this obviously will not work since number of channel contexts will be
more than one and hence drivers would need to pass the channel information
as well on which the radar is detected.
Also, when radar is detected in one of the links, other link's CAC should
not be cancelled.
Hence, in order to support DFS with MLO, do the following changes -
* Add channel context conf pointer as an argument to the function
ieee80211_radar_detected(). During MLO, drivers would have to pass on
which channel context conf radar is detected. Otherwise, drivers could
just pass NULL.
* ieee80211_radar_detected() will iterate over all channel contexts
present and
* if channel context conf is passed, only mark that as radar
detected
* if NULL is passed, then mark all channel contexts as radar
detected
* Then as usual, schedule the radar detected work.
* In the worker, go over all the contexts again and for all such context
which is marked with radar detected, cancel the ongoing CAC by calling
ieee80211_dfs_cac_cancel() and then notify cfg80211 via
cfg80211_radar_event().
* To cancel the CAC, pass the channel context as well where radar is
detected to ieee80211_dfs_cac_cancel(). This ensures that CAC is
canceled only on the links using the provided context, leaving other
links unaffected.
This would also help in scenarios where there is split phy 5 GHz radio,
which is capable of DFS channels in both lower and upper band. In this
case, simultaneous radars can be detected.
Signed-off-by: Aditya Kumar Singh <quic_adisi@quicinc.com>
Link: https://patch.msgid.link/20240906064426.2101315-9-quic_adisi@quicinc.com
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2024-09-06 12:14:26 +05:30
|
|
|
|
2024-09-06 12:14:24 +05:30
|
|
|
|
2013-02-08 18:16:20 +01:00
|
|
|
|
2021-01-22 16:19:43 +01:00
|
|
|
|
2017-04-26 10:58:53 +03:00
|
|
|
|
2013-02-08 18:16:20 +01:00
|
|
|
|
2024-09-06 12:14:24 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-02-08 18:16:20 +01:00
|
|
|
|
wifi: mac80211: handle ieee80211_radar_detected() for MLO
Currently DFS works under assumption there could be only one channel
context in the hardware. Hence, drivers just calls the function
ieee80211_radar_detected() passing the hardware structure. However, with
MLO, this obviously will not work since number of channel contexts will be
more than one and hence drivers would need to pass the channel information
as well on which the radar is detected.
Also, when radar is detected in one of the links, other link's CAC should
not be cancelled.
Hence, in order to support DFS with MLO, do the following changes -
* Add channel context conf pointer as an argument to the function
ieee80211_radar_detected(). During MLO, drivers would have to pass on
which channel context conf radar is detected. Otherwise, drivers could
just pass NULL.
* ieee80211_radar_detected() will iterate over all channel contexts
present and
* if channel context conf is passed, only mark that as radar
detected
* if NULL is passed, then mark all channel contexts as radar
detected
* Then as usual, schedule the radar detected work.
* In the worker, go over all the contexts again and for all such context
which is marked with radar detected, cancel the ongoing CAC by calling
ieee80211_dfs_cac_cancel() and then notify cfg80211 via
cfg80211_radar_event().
* To cancel the CAC, pass the channel context as well where radar is
detected to ieee80211_dfs_cac_cancel(). This ensures that CAC is
canceled only on the links using the provided context, leaving other
links unaffected.
This would also help in scenarios where there is split phy 5 GHz radio,
which is capable of DFS channels in both lower and upper band. In this
case, simultaneous radars can be detected.
Signed-off-by: Aditya Kumar Singh <quic_adisi@quicinc.com>
Link: https://patch.msgid.link/20240906064426.2101315-9-quic_adisi@quicinc.com
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2024-09-06 12:14:26 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-01-30 09:25:11 +05:30
|
|
|
|
2024-09-06 12:14:24 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-02-08 18:16:20 +01:00
|
|
|
|
2024-09-06 12:14:24 +05:30
|
|
|
|
2013-02-08 18:16:20 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-08-28 13:59:38 +02:00
|
|
|
|
|
|
|
|
|
2013-02-08 18:16:20 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
wifi: mac80211: handle ieee80211_radar_detected() for MLO
Currently DFS works under assumption there could be only one channel
context in the hardware. Hence, drivers just calls the function
ieee80211_radar_detected() passing the hardware structure. However, with
MLO, this obviously will not work since number of channel contexts will be
more than one and hence drivers would need to pass the channel information
as well on which the radar is detected.
Also, when radar is detected in one of the links, other link's CAC should
not be cancelled.
Hence, in order to support DFS with MLO, do the following changes -
* Add channel context conf pointer as an argument to the function
ieee80211_radar_detected(). During MLO, drivers would have to pass on
which channel context conf radar is detected. Otherwise, drivers could
just pass NULL.
* ieee80211_radar_detected() will iterate over all channel contexts
present and
* if channel context conf is passed, only mark that as radar
detected
* if NULL is passed, then mark all channel contexts as radar
detected
* Then as usual, schedule the radar detected work.
* In the worker, go over all the contexts again and for all such context
which is marked with radar detected, cancel the ongoing CAC by calling
ieee80211_dfs_cac_cancel() and then notify cfg80211 via
cfg80211_radar_event().
* To cancel the CAC, pass the channel context as well where radar is
detected to ieee80211_dfs_cac_cancel(). This ensures that CAC is
canceled only on the links using the provided context, leaving other
links unaffected.
This would also help in scenarios where there is split phy 5 GHz radio,
which is capable of DFS channels in both lower and upper band. In this
case, simultaneous radars can be detected.
Signed-off-by: Aditya Kumar Singh <quic_adisi@quicinc.com>
Link: https://patch.msgid.link/20240906064426.2101315-9-quic_adisi@quicinc.com
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2024-09-06 12:14:26 +05:30
|
|
|
|
2026-05-05 15:15:40 +02:00
|
|
|
|
2014-10-10 12:43:23 +02:00
|
|
|
|
2023-08-28 14:00:03 +02:00
|
|
|
|
2023-08-28 14:00:05 +02:00
|
|
|
|
2026-05-05 15:15:40 +02:00
|
|
|
|
2014-10-10 12:43:23 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
wifi: mac80211: handle ieee80211_radar_detected() for MLO
Currently DFS works under assumption there could be only one channel
context in the hardware. Hence, drivers just calls the function
ieee80211_radar_detected() passing the hardware structure. However, with
MLO, this obviously will not work since number of channel contexts will be
more than one and hence drivers would need to pass the channel information
as well on which the radar is detected.
Also, when radar is detected in one of the links, other link's CAC should
not be cancelled.
Hence, in order to support DFS with MLO, do the following changes -
* Add channel context conf pointer as an argument to the function
ieee80211_radar_detected(). During MLO, drivers would have to pass on
which channel context conf radar is detected. Otherwise, drivers could
just pass NULL.
* ieee80211_radar_detected() will iterate over all channel contexts
present and
* if channel context conf is passed, only mark that as radar
detected
* if NULL is passed, then mark all channel contexts as radar
detected
* Then as usual, schedule the radar detected work.
* In the worker, go over all the contexts again and for all such context
which is marked with radar detected, cancel the ongoing CAC by calling
ieee80211_dfs_cac_cancel() and then notify cfg80211 via
cfg80211_radar_event().
* To cancel the CAC, pass the channel context as well where radar is
detected to ieee80211_dfs_cac_cancel(). This ensures that CAC is
canceled only on the links using the provided context, leaving other
links unaffected.
This would also help in scenarios where there is split phy 5 GHz radio,
which is capable of DFS channels in both lower and upper band. In this
case, simultaneous radars can be detected.
Signed-off-by: Aditya Kumar Singh <quic_adisi@quicinc.com>
Link: https://patch.msgid.link/20240906064426.2101315-9-quic_adisi@quicinc.com
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2024-09-06 12:14:26 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-10-10 12:43:23 +02:00
|
|
|
|
2013-02-08 18:16:20 +01:00
|
|
|
|
wifi: mac80211: handle ieee80211_radar_detected() for MLO
Currently DFS works under assumption there could be only one channel
context in the hardware. Hence, drivers just calls the function
ieee80211_radar_detected() passing the hardware structure. However, with
MLO, this obviously will not work since number of channel contexts will be
more than one and hence drivers would need to pass the channel information
as well on which the radar is detected.
Also, when radar is detected in one of the links, other link's CAC should
not be cancelled.
Hence, in order to support DFS with MLO, do the following changes -
* Add channel context conf pointer as an argument to the function
ieee80211_radar_detected(). During MLO, drivers would have to pass on
which channel context conf radar is detected. Otherwise, drivers could
just pass NULL.
* ieee80211_radar_detected() will iterate over all channel contexts
present and
* if channel context conf is passed, only mark that as radar
detected
* if NULL is passed, then mark all channel contexts as radar
detected
* Then as usual, schedule the radar detected work.
* In the worker, go over all the contexts again and for all such context
which is marked with radar detected, cancel the ongoing CAC by calling
ieee80211_dfs_cac_cancel() and then notify cfg80211 via
cfg80211_radar_event().
* To cancel the CAC, pass the channel context as well where radar is
detected to ieee80211_dfs_cac_cancel(). This ensures that CAC is
canceled only on the links using the provided context, leaving other
links unaffected.
This would also help in scenarios where there is split phy 5 GHz radio,
which is capable of DFS channels in both lower and upper band. In this
case, simultaneous radars can be detected.
Signed-off-by: Aditya Kumar Singh <quic_adisi@quicinc.com>
Link: https://patch.msgid.link/20240906064426.2101315-9-quic_adisi@quicinc.com
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2024-09-06 12:14:26 +05:30
|
|
|
|
2013-02-08 18:16:20 +01:00
|
|
|
|
wifi: mac80211: handle ieee80211_radar_detected() for MLO
Currently DFS works under assumption there could be only one channel
context in the hardware. Hence, drivers just calls the function
ieee80211_radar_detected() passing the hardware structure. However, with
MLO, this obviously will not work since number of channel contexts will be
more than one and hence drivers would need to pass the channel information
as well on which the radar is detected.
Also, when radar is detected in one of the links, other link's CAC should
not be cancelled.
Hence, in order to support DFS with MLO, do the following changes -
* Add channel context conf pointer as an argument to the function
ieee80211_radar_detected(). During MLO, drivers would have to pass on
which channel context conf radar is detected. Otherwise, drivers could
just pass NULL.
* ieee80211_radar_detected() will iterate over all channel contexts
present and
* if channel context conf is passed, only mark that as radar
detected
* if NULL is passed, then mark all channel contexts as radar
detected
* Then as usual, schedule the radar detected work.
* In the worker, go over all the contexts again and for all such context
which is marked with radar detected, cancel the ongoing CAC by calling
ieee80211_dfs_cac_cancel() and then notify cfg80211 via
cfg80211_radar_event().
* To cancel the CAC, pass the channel context as well where radar is
detected to ieee80211_dfs_cac_cancel(). This ensures that CAC is
canceled only on the links using the provided context, leaving other
links unaffected.
This would also help in scenarios where there is split phy 5 GHz radio,
which is capable of DFS channels in both lower and upper band. In this
case, simultaneous radars can be detected.
Signed-off-by: Aditya Kumar Singh <quic_adisi@quicinc.com>
Link: https://patch.msgid.link/20240906064426.2101315-9-quic_adisi@quicinc.com
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2024-09-06 12:14:26 +05:30
|
|
|
|
2013-02-08 18:16:20 +01:00
|
|
|
|
|
|
|
|
|
wifi: mac80211: handle ieee80211_radar_detected() for MLO
Currently DFS works under assumption there could be only one channel
context in the hardware. Hence, drivers just calls the function
ieee80211_radar_detected() passing the hardware structure. However, with
MLO, this obviously will not work since number of channel contexts will be
more than one and hence drivers would need to pass the channel information
as well on which the radar is detected.
Also, when radar is detected in one of the links, other link's CAC should
not be cancelled.
Hence, in order to support DFS with MLO, do the following changes -
* Add channel context conf pointer as an argument to the function
ieee80211_radar_detected(). During MLO, drivers would have to pass on
which channel context conf radar is detected. Otherwise, drivers could
just pass NULL.
* ieee80211_radar_detected() will iterate over all channel contexts
present and
* if channel context conf is passed, only mark that as radar
detected
* if NULL is passed, then mark all channel contexts as radar
detected
* Then as usual, schedule the radar detected work.
* In the worker, go over all the contexts again and for all such context
which is marked with radar detected, cancel the ongoing CAC by calling
ieee80211_dfs_cac_cancel() and then notify cfg80211 via
cfg80211_radar_event().
* To cancel the CAC, pass the channel context as well where radar is
detected to ieee80211_dfs_cac_cancel(). This ensures that CAC is
canceled only on the links using the provided context, leaving other
links unaffected.
This would also help in scenarios where there is split phy 5 GHz radio,
which is capable of DFS channels in both lower and upper band. In this
case, simultaneous radars can be detected.
Signed-off-by: Aditya Kumar Singh <quic_adisi@quicinc.com>
Link: https://patch.msgid.link/20240906064426.2101315-9-quic_adisi@quicinc.com
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2024-09-06 12:14:26 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-02-08 18:16:20 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
wifi: mac80211: handle ieee80211_radar_detected() for MLO
Currently DFS works under assumption there could be only one channel
context in the hardware. Hence, drivers just calls the function
ieee80211_radar_detected() passing the hardware structure. However, with
MLO, this obviously will not work since number of channel contexts will be
more than one and hence drivers would need to pass the channel information
as well on which the radar is detected.
Also, when radar is detected in one of the links, other link's CAC should
not be cancelled.
Hence, in order to support DFS with MLO, do the following changes -
* Add channel context conf pointer as an argument to the function
ieee80211_radar_detected(). During MLO, drivers would have to pass on
which channel context conf radar is detected. Otherwise, drivers could
just pass NULL.
* ieee80211_radar_detected() will iterate over all channel contexts
present and
* if channel context conf is passed, only mark that as radar
detected
* if NULL is passed, then mark all channel contexts as radar
detected
* Then as usual, schedule the radar detected work.
* In the worker, go over all the contexts again and for all such context
which is marked with radar detected, cancel the ongoing CAC by calling
ieee80211_dfs_cac_cancel() and then notify cfg80211 via
cfg80211_radar_event().
* To cancel the CAC, pass the channel context as well where radar is
detected to ieee80211_dfs_cac_cancel(). This ensures that CAC is
canceled only on the links using the provided context, leaving other
links unaffected.
This would also help in scenarios where there is split phy 5 GHz radio,
which is capable of DFS channels in both lower and upper band. In this
case, simultaneous radars can be detected.
Signed-off-by: Aditya Kumar Singh <quic_adisi@quicinc.com>
Link: https://patch.msgid.link/20240906064426.2101315-9-quic_adisi@quicinc.com
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2024-09-06 12:14:26 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-08-28 13:59:38 +02:00
|
|
|
|
2013-02-08 18:16:20 +01:00
|
|
|
|
|
|
|
|
|
2013-08-28 13:41:29 +02:00
|
|
|
|
2024-01-29 19:34:36 +01:00
|
|
|
|
|
|
|
|
|
2013-08-28 13:41:29 +02:00
|
|
|
|
2024-01-29 19:34:49 +01:00
|
|
|
|
2024-01-29 19:34:36 +01:00
|
|
|
|
2013-08-28 13:41:29 +02:00
|
|
|
|
2024-01-29 19:34:36 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-01-29 19:34:49 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-08-28 13:41:29 +02:00
|
|
|
|
2024-01-29 19:34:36 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-08-28 13:41:29 +02:00
|
|
|
|
|
|
|
|
|
2024-01-29 19:34:36 +01:00
|
|
|
|
|
|
|
|
|
2024-01-29 19:34:49 +01:00
|
|
|
|
2013-08-28 13:41:29 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-01-29 19:34:36 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-01-29 19:34:49 +01:00
|
|
|
|
2013-08-28 13:41:29 +02:00
|
|
|
|
|
|
|
|
|
2024-01-29 19:34:48 +01:00
|
|
|
|
2024-01-29 19:34:36 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-08-28 13:41:29 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-01-29 19:34:36 +01:00
|
|
|
|
2013-08-28 13:41:29 +02:00
|
|
|
|
|
|
|
|
|
2024-01-29 19:34:48 +01:00
|
|
|
|
2024-01-29 19:34:36 +01:00
|
|
|
|
2013-08-28 13:41:29 +02:00
|
|
|
|
2022-02-14 17:30:00 +01:00
|
|
|
|
2024-01-29 19:34:48 +01:00
|
|
|
|
2024-01-29 19:34:36 +01:00
|
|
|
|
2013-08-28 13:41:29 +02:00
|
|
|
|
2020-06-01 23:22:47 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-01-29 19:34:36 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-08-28 13:41:29 +02:00
|
|
|
|
|
|
|
|
|
2024-01-29 19:34:48 +01:00
|
|
|
|
2024-01-29 19:34:49 +01:00
|
|
|
|
|
|
|
|
|
2024-01-29 19:34:48 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-04-28 11:25:35 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-01-29 19:34:49 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-08-28 13:41:29 +02:00
|
|
|
|
|
|
|
|
|
2013-10-01 16:45:43 +03:00
|
|
|
|
2026-04-15 14:42:06 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-10-14 19:08:28 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
wifi: move action code from per-type frame structs
The action code actually serves to identify the type of action
frame, so it really isn't part of the per-type structure. Pull
it out and have it in the general action frame format.
In theory, whether or not the action code is present in this
way is up to each category, but all categories that are defined
right now all have that value.
While at it, and since this change requires changing all users,
remove the 'u' and make it an anonymous union in this case, so
that all code using this changes.
Change IEEE80211_MIN_ACTION_SIZE to take an argument which says
how much of the frame is needed, e.g. category, action_code or
the specific frame type that's defined in the union. Again this
also ensures that all code is updated.
In some cases, fix bugs where the SKB length was checked after
having accessed beyond the checked length, in particular in FTM
code, e.g. ieee80211_is_ftm().
Link: https://patch.msgid.link/20260226183607.67e71846b59e.I9a24328e3ffcaae179466a935f1c3345029f9961@changeid
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2026-02-26 18:36:07 +01:00
|
|
|
|
2013-10-14 19:08:28 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-05-23 17:00:42 +02:00
|
|
|
|
2013-10-14 19:08:28 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
networking: convert many more places to skb_put_zero()
There were many places that my previous spatch didn't find,
as pointed out by yuan linyu in various patches.
The following spatch found many more and also removes the
now unnecessary casts:
@@
identifier p, p2;
expression len;
expression skb;
type t, t2;
@@
(
-p = skb_put(skb, len);
+p = skb_put_zero(skb, len);
|
-p = (t)skb_put(skb, len);
+p = skb_put_zero(skb, len);
)
... when != p
(
p2 = (t2)p;
-memset(p2, 0, len);
|
-memset(p, 0, len);
)
@@
type t, t2;
identifier p, p2;
expression skb;
@@
t *p;
...
(
-p = skb_put(skb, sizeof(t));
+p = skb_put_zero(skb, sizeof(t));
|
-p = (t *)skb_put(skb, sizeof(t));
+p = skb_put_zero(skb, sizeof(t));
)
... when != p
(
p2 = (t2)p;
-memset(p2, 0, sizeof(*p));
|
-memset(p, 0, sizeof(*p));
)
@@
expression skb, len;
@@
-memset(skb_put(skb, len), 0, len);
+skb_put_zero(skb, len);
Apply it to the tree (with one manual fixup to keep the
comment in vxlan.c, which spatch removed.)
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2017-06-16 14:29:19 +02:00
|
|
|
|
2013-10-14 19:08:28 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
wifi: move action code from per-type frame structs
The action code actually serves to identify the type of action
frame, so it really isn't part of the per-type structure. Pull
it out and have it in the general action frame format.
In theory, whether or not the action code is present in this
way is up to each category, but all categories that are defined
right now all have that value.
While at it, and since this change requires changing all users,
remove the 'u' and make it an anonymous union in this case, so
that all code using this changes.
Change IEEE80211_MIN_ACTION_SIZE to take an argument which says
how much of the frame is needed, e.g. category, action_code or
the specific frame type that's defined in the union. Again this
also ensures that all code is updated.
In some cases, fix bugs where the SKB length was checked after
having accessed beyond the checked length, in particular in FTM
code, e.g. ieee80211_is_ftm().
Link: https://patch.msgid.link/20260226183607.67e71846b59e.I9a24328e3ffcaae179466a935f1c3345029f9961@changeid
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2026-02-26 18:36:07 +01:00
|
|
|
|
2013-10-14 19:08:28 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-11-12 10:31:48 +08:00
|
|
|
|
2013-10-14 19:08:28 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-05-23 17:00:42 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-10-14 19:08:28 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-03-24 14:23:27 +02:00
|
|
|
|
2013-12-16 21:49:14 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-10-27 08:35:11 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-12-16 21:49:14 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-12-19 10:25:15 -08:00
|
|
|
|
2025-07-17 17:42:04 +10:00
|
|
|
|
2013-12-19 10:25:15 -08:00
|
|
|
|
|
|
|
|
|
2025-06-21 22:32:09 +10:00
|
|
|
|
2013-12-19 10:25:15 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-02-13 11:31:59 +02:00
|
|
|
|
2025-07-17 17:42:04 +10:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-06-25 12:35:07 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-05-30 18:35:23 +02:00
|
|
|
|
2014-06-25 12:35:07 +02:00
|
|
|
|
|
|
|
|
|
2023-08-28 14:00:03 +02:00
|
|
|
|
2014-06-25 12:35:07 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
wifi: mac80211: remove chanctx to link back-references
Each link can currently use a chanctx and have another one
reserved, and both of these are also tracked backwards in
the assigned_links and reserved_links lists. If we consider
that there aren't *that* many links, this duplicate book-
keeping isn't necessary.
(I think it used to be necessary before the wiphy locking
changes, when chanctx_mtx existed, because we couldn't do
any interface iterations while holding only chanctx_mtx.)
Additionally, for NAN, we're going to want to track which
chanctxs are in use by the (group of) NAN interfaces. For
those, links don't really make sense as such, so chanctxs
need to be assigned to a different data structure.
Thus, as a first step, remove those back-lists of users
(right now only links) of each channel context. This is a
very basic conversion, ieee80211_vif_use_reserved_switch()
should made to iterate smarter.
Link: https://patch.msgid.link/20251105160431.dbeea1c42e76.I8d273c407274e1c05a4778aa20b56a9f326e87a7@changeid
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2025-11-05 16:03:43 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
wifi: mac80211: introduce 'channel request'
For channel contexts, mac80211 currently uses the cfg80211
chandef struct (control channel, center freq(s), width) to
define towards drivers and internally how these behave. In
fact, there are _two_ such structs used, where the min_def
can reduce bandwidth according to the stations connected.
Unfortunately, with EHT this is longer be sufficient, at
least not for all hardware. EHT requires that non-AP STAs
that are connected to an AP with a lower bandwidth than it
(the AP) advertises (e.g. 160 MHz STA connected to 320 MHz
AP) still be able to receive downlink OFDMA and respond to
trigger frames for uplink OFDMA that specify the position
and bandwidth for the non-AP STA relative to the channel
the AP is using. Therefore, they need to be aware of this,
and at least for some hardware (e.g. Intel) this awareness
is in the hardware. As a result, use of the "same" channel
may need to be split over two channel contexts where they
differ by the AP being used.
As a first step, introduce a concept of a channel request
('chanreq') for each interface, to control the context it
requests. This step does nothing but reorganise the code,
so that later the AP's chandef can be added to the request
in order to handle the EHT case described above.
Link: https://msgid.link/20240129194108.2e88e48bd2e9.I4256183debe975c5ed71621611206fdbb69ba330@changeid
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2024-01-29 19:34:40 +01:00
|
|
|
|
2022-05-30 18:35:23 +02:00
|
|
|
|
2014-06-25 12:35:07 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-05-27 14:11:44 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-08-12 12:53:29 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-05-27 14:11:44 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-07-09 10:38:35 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-05-27 22:51:43 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-07-09 10:38:35 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-05-27 22:51:43 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-07-09 10:38:35 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-05-27 22:51:43 +03:00
|
|
|
|
|
|
|
|
|
2014-02-13 11:31:59 +02:00
|
|
|
|
2026-05-27 22:51:43 +03:00
|
|
|
|
|
|
|
|
|
2014-02-13 11:31:59 +02:00
|
|
|
|
|
|
|
|
|
2016-10-12 18:25:35 +05:30
|
|
|
|
2026-05-27 22:51:43 +03:00
|
|
|
|
|
|
|
|
|
2016-10-12 18:25:35 +05:30
|
|
|
|
2024-07-09 10:38:35 +02:00
|
|
|
|
2014-02-13 11:31:59 +02:00
|
|
|
|
2023-08-28 14:00:03 +02:00
|
|
|
|
2014-02-13 11:31:59 +02:00
|
|
|
|
2026-05-27 22:51:43 +03:00
|
|
|
|
2014-02-13 11:31:59 +02:00
|
|
|
|
|
|
|
|
|
2026-05-27 22:51:43 +03:00
|
|
|
|
2014-02-27 11:07:21 +02:00
|
|
|
|
2014-02-13 11:31:59 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-10-21 14:25:14 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-02-13 11:31:59 +02:00
|
|
|
|
2019-07-22 12:44:50 +05:30
|
|
|
|
2026-05-27 22:51:43 +03:00
|
|
|
|
2014-02-13 11:31:59 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-10-12 18:25:35 +05:30
|
|
|
|
|
|
|
|
|
2014-02-13 11:31:59 +02:00
|
|
|
|
|
|
|
|
|
2016-10-12 18:25:35 +05:30
|
|
|
|
2014-02-13 11:31:59 +02:00
|
|
|
|
2024-07-09 10:38:35 +02:00
|
|
|
|
|
|
|
|
|
2026-05-27 22:51:43 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-10-12 18:25:35 +05:30
|
|
|
|
2014-02-13 11:31:59 +02:00
|
|
|
|
|
|
|
|
|
2016-10-12 18:25:35 +05:30
|
|
|
|
2014-02-13 11:31:59 +02:00
|
|
|
|
2014-04-09 15:29:23 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-07-09 10:38:35 +02:00
|
|
|
|
2014-04-09 15:29:23 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-07-09 10:38:31 +02:00
|
|
|
|
2024-07-09 10:38:35 +02:00
|
|
|
|
2024-07-09 10:38:31 +02:00
|
|
|
|
2014-04-09 15:29:23 +02:00
|
|
|
|
2023-08-28 14:00:03 +02:00
|
|
|
|
2014-04-09 15:29:23 +02:00
|
|
|
|
2026-05-27 22:51:43 +03:00
|
|
|
|
2014-04-09 15:29:23 +02:00
|
|
|
|
2016-10-12 18:25:35 +05:30
|
|
|
|
|
|
|
|
|
2014-04-09 15:29:23 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-09-21 19:28:05 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-04-09 15:29:23 +02:00
|
|
|
|
2014-07-17 17:14:23 +03:00
|
|
|
|
2020-09-21 19:28:15 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-07-17 17:14:23 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-03-27 21:30:37 +01:00
|
|
|
|
2016-01-27 15:26:12 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-09-22 19:04:20 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-01-27 15:26:12 +01:00
|
|
|
|
|
|
|
|
|
2016-09-22 19:04:20 +02:00
|
|
|
|
2016-01-27 15:26:12 +01:00
|
|
|
|
|
|
|
|
|
2016-09-22 19:04:20 +02:00
|
|
|
|
2016-01-27 15:26:12 +01:00
|
|
|
|
|
|
|
|
|
2016-10-18 23:12:12 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-09-21 19:28:10 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-02-14 17:30:01 +01:00
|
|
|
|
2024-01-29 20:19:36 +01:00
|
|
|
|
2024-01-29 20:19:27 +01:00
|
|
|
|
2022-02-14 17:30:01 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-08-16 11:26:23 +02:00
|
|
|
|
2022-02-14 17:30:01 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-01-29 20:19:27 +01:00
|
|
|
|
|
|
|
|
|
2022-02-14 17:30:01 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-01-29 20:19:27 +01:00
|
|
|
|
2022-08-16 11:26:23 +02:00
|
|
|
|
2022-02-14 17:30:01 +01:00
|
|
|
|
2022-08-16 11:26:23 +02:00
|
|
|
|
|
|
|
|
|
2022-02-14 17:30:01 +01:00
|
|
|
|
2023-03-28 01:07:41 +08:00
|
|
|
|
2022-02-14 17:30:01 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-01-29 20:19:36 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-02-14 17:30:01 +01:00
|
|
|
|
2024-01-29 20:19:36 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-01-29 20:19:28 +01:00
|
|
|
|
2022-02-14 17:30:01 +01:00
|
|
|
|
2024-01-29 20:19:28 +01:00
|
|
|
|
2022-02-14 17:30:01 +01:00
|
|
|
|
|
|
|
|
|
2024-01-29 20:19:28 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-02-14 17:30:01 +01:00
|
|
|
|
|
|
|
|
|
2024-01-29 20:19:36 +01:00
|
|
|
|
2022-02-14 17:30:01 +01:00
|
|
|
|
2024-01-29 20:19:28 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-02-14 17:30:01 +01:00
|
|
|
|
2024-01-29 20:19:28 +01:00
|
|
|
|
2022-02-14 17:30:01 +01:00
|
|
|
|
|
|
|
|
|
2024-01-29 20:19:36 +01:00
|
|
|
|
|
|
|
|
|
2022-02-14 17:30:01 +01:00
|
|
|
|
2024-01-29 20:19:36 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-02-14 17:30:01 +01:00
|
|
|
|
2024-01-29 20:19:28 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-01-29 20:19:36 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-01-29 20:19:28 +01:00
|
|
|
|
2024-01-29 20:19:36 +01:00
|
|
|
|
2024-01-29 20:19:28 +01:00
|
|
|
|
2022-02-14 17:30:01 +01:00
|
|
|
|
2024-01-29 20:19:36 +01:00
|
|
|
|
|
|
|
|
|
2022-02-14 17:30:01 +01:00
|
|
|
|
2024-01-29 20:19:36 +01:00
|
|
|
|
2022-02-14 17:30:01 +01:00
|
|
|
|
2024-01-29 19:34:36 +01:00
|
|
|
|
2026-01-30 16:21:07 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-04-28 10:36:57 +02:00
|
|
|
|
2026-01-30 16:21:07 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-01-29 19:34:36 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-01-30 16:21:07 +01:00
|
|
|
|
2024-01-29 19:34:36 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-05-06 21:37:56 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-09-08 14:13:06 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|