28 Sep, 2020

1 commit


18 Sep, 2020

1 commit

  • In order to unify the tx status path, the hw 802.11 encapsulation flag
    needs to survive the trip to the tx status call.
    Since we don't have any free bits in info->flags, we need to move one.
    IEEE80211_TX_INTFL_NEED_TXPROCESSING is only used internally in mac80211,
    and only before the call into the driver.

    Signed-off-by: Felix Fietkau
    Link: https://lore.kernel.org/r/20200908123702.88454-10-nbd@nbd.name
    Signed-off-by: Johannes Berg

    Felix Fietkau
     

19 Jun, 2019

1 commit

  • Based on 2 normalized pattern(s):

    this program is free software you can redistribute it and or modify
    it under the terms of the gnu general public license version 2 as
    published by the free software foundation

    this program is free software you can redistribute it and or modify
    it under the terms of the gnu general public license version 2 as
    published by the free software foundation #

    extracted by the scancode license scanner the SPDX license identifier

    GPL-2.0-only

    has been chosen to replace the boilerplate/reference in 4122 file(s).

    Signed-off-by: Thomas Gleixner
    Reviewed-by: Enrico Weigelt
    Reviewed-by: Kate Stewart
    Reviewed-by: Allison Randal
    Cc: linux-spdx@vger.kernel.org
    Link: https://lkml.kernel.org/r/20190604081206.933168790@linutronix.de
    Signed-off-by: Greg Kroah-Hartman

    Thomas Gleixner
     

16 Jun, 2017

2 commits

  • It seems like a historic accident that these return unsigned char *,
    and in many places that means casts are required, more often than not.

    Make these functions (skb_put, __skb_put and pskb_put) return void *
    and remove all the casts across the tree, adding a (u8 *) cast only
    where the unsigned char pointer was used directly, all done with the
    following spatch:

    @@
    expression SKB, LEN;
    typedef u8;
    identifier fn = { skb_put, __skb_put };
    @@
    - *(fn(SKB, LEN))
    + *(u8 *)fn(SKB, LEN)

    @@
    expression E, SKB, LEN;
    identifier fn = { skb_put, __skb_put };
    type T;
    @@
    - E = ((T *)(fn(SKB, LEN)))
    + E = fn(SKB, LEN)

    which actually doesn't cover pskb_put since there are only three
    users overall.

    A handful of stragglers were converted manually, notably a macro in
    drivers/isdn/i4l/isdn_bsdcomp.c and, oddly enough, one of the many
    instances in net/bluetooth/hci_sock.c. In the former file, I also
    had to fix one whitespace problem spatch introduced.

    Signed-off-by: Johannes Berg
    Signed-off-by: David S. Miller

    Johannes Berg
     
  • 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
    Signed-off-by: David S. Miller

    Johannes Berg
     

17 Jul, 2015

2 commits

  • According to 802.11-2012 13.3.1, a mesh STA should assign an AID
    upon receipt of a mesh peering open frame rather than using the link
    id of the peer. Using the peer link id has two potential issues:
    it may not be unique among the peers, and by its nature it is random,
    so the TIM may not compress well.

    In preparation for allocating it properly, use sta->sta.aid, but keep
    the existing behavior of using the plid in the aid we send.

    Signed-off-by: Bob Copeland
    Signed-off-by: Johannes Berg

    Bob Copeland
     
  • There are now a fairly large number of mesh fields that really
    aren't needed in any other modes; move those into their own
    structure and allocate them separately.

    Signed-off-by: Johannes Berg

    Johannes Berg
     

05 Mar, 2014

1 commit

  • Avoid leaking data by sending uninitialized memory and setting an
    invalid (non-zero) fragment number (the sequence number is ignored
    anyway) by setting the seq_ctrl field to zero.

    Cc: stable@vger.kernel.org
    Fixes: 3f52b7e328c5 ("mac80211: mesh power save basics")
    Fixes: ce662b44ce22 ("mac80211: send (QoS) Null if no buffered frames")
    Reviewed-by: Emmanuel Grumbach
    Signed-off-by: Johannes Berg

    Johannes Berg
     

26 Nov, 2013

2 commits

  • Use put_unaligned_le16 in mesh_plink_frame_tx.

    Signed-off-by: Chun-Yeow Yeoh
    Signed-off-by: Johannes Berg

    Chun-Yeow Yeoh
     
  • 802.11-2012 13.3.1 implicitly limits the mesh local link
    ID range to that of AID, since for mesh PS the local link
    ID must be indicated in the TIM IE, which only holds
    IEEE80211_MAX_AID bits.

    Also the code was allowing a local link ID of 0, but this
    is not correct since that TIM bit is used for indicating
    buffered mcast frames.

    Generate a random, unique, link ID from 1 - 2007, and drop
    a modulo conversion for the local link ID, but keep it for
    the peer link ID in case he chose something > MAX_AID.

    Signed-off-by: Thomas Pedersen
    Signed-off-by: Johannes Berg

    Thomas Pedersen
     

28 Oct, 2013

1 commit

  • This patch fixes errors in the mesh powersave logic which
    cause that remote peers do not get peer power mode change
    notifications and mesh peer service periods (MPSPs) got
    stuck.

    When closing a peer link, set the (now invalid) peer-specific
    power mode to 'unknown'.

    Avoid overhead when local power mode is unchanged.

    Reliably clear MPSP flags on peering status update.

    Avoid MPSP flags getting stuck by not requesting a further
    MPSP ownership if we already are an MPSP owner.

    Signed-off-by: Marco Porsch
    Signed-off-by: Johannes Berg

    Marco Porsch
     

22 Jul, 2013

1 commit

  • This patch is intended to avoid the buffering to non-assoc mesh STA
    and also to avoid the triggering of frame to non-assoc mesh STA which
    could cause kernel panic in specific hw.

    One of the examples, is kernel panic happens to ath9k if user space
    inserts the mesh STA and not proceed with the SAE and AMPE, and later
    the same mesh STA is detected again. The sta_state of the mesh STA remains
    at IEEE80211_STA_NONE and if the ieee80211_sta_ps_deliver_wakeup is called
    and subsequently the ath_tx_aggr_wakeup, the kernel panic due to
    ath_tx_node_init is not called before to initialize the require data
    structures.

    This issue is reported by Cedric Voncken before.
    http://www.spinics.net/lists/linux-wireless/msg106342.html

    [] ath_tx_aggr_wakeup+0x44/0xcc [ath9k]
    [] ieee80211_sta_ps_deliver_wakeup+0xb8/0x208 [mac80211]
    [] ieee80211_mps_sta_status_update+0x94/0x108 [mac80211]
    [] ieee80211_sta_ps_transition+0xc94/0x34d8 [mac80211]
    [] nf_iterate+0x98/0x104
    [] ieee80211_sta_ps_transition+0x345c/0x34d8 [mac80211]

    Signed-off-by: Chun-Yeow Yeoh
    Signed-off-by: Johannes Berg

    Chun-Yeow Yeoh
     

15 Feb, 2013

1 commit

  • A few mesh utility functions will call
    ieee80211_bss_info_change_notify(), and then the caller
    might notify the driver of the same change again. Avoid
    this redundancy by propagating the BSS changes and
    generally calling bss_info_change_notify() once per
    change.

    Signed-off-by: Thomas Pedersen
    Signed-off-by: Johannes Berg

    Thomas Pedersen
     

05 Feb, 2013

1 commit

  • Add routines to
    - maintain a PS mode for each peer and a non-peer PS mode
    - indicate own PS mode in transmitted frames
    - track neighbor STAs power modes
    - buffer frames when neighbors are in PS mode
    - add TIM and Awake Window IE to beacons
    - release frames in Mesh Peer Service Periods

    Add local_pm to sta_info to represent the link-specific power
    mode at this station towards the remote station. When a peer
    link is established, use the default power mode stored in mesh
    config. Update the PS status if the peering status of a neighbor
    changes.
    Maintain a mesh power mode for non-peer mesh STAs. Set the
    non-peer power mode to active mode during peering. Authenticated
    mesh peering is currently not working when either node is
    configured to be in power save mode.

    Indicate the current power mode in transmitted frames. Use QoS
    Nulls to indicate mesh power mode transitions.
    For performance reasons, calls to the function setting the frame
    flags are placed in HWMP routing routines, as there the STA
    pointer is already available.

    Add peer_pm to sta_info to represent the peer's link-specific
    power mode towards the local station. Add nonpeer_pm to
    represent the peer's power mode towards all non-peer stations.
    Track power modes based on received frames.

    Add the ps_data structure to ieee80211_if_mesh (for TIM map, PS
    neighbor counter and group-addressed frame buffer).

    Set WLAN_STA_PS flag for STA in PS mode to use the unicast frame
    buffering routines in the tx path. Update num_sta_ps to buffer
    and release group-addressed frames after DTIM beacons.

    Announce the awake window duration in beacons if in light or
    deep sleep mode towards any peer or non-peer. Create a TIM IE
    similarly to AP mode and add it to mesh beacons. Parse received
    Awake Window IEs and check TIM IEs for buffered frames.

    Release frames towards peers in mesh Peer Service Periods. Use
    the corresponding trigger frames and monitor the MPSP status.
    Append a QoS Null as trigger frame if neccessary to properly end
    the MPSP. Currently, in HT channels MPSPs behave imperfectly and
    show large delay spikes and frame losses.

    Signed-off-by: Marco Porsch
    Signed-off-by: Ivan Bezyazychnyy
    Signed-off-by: Mike Krinkin
    Signed-off-by: Max Filippov
    Signed-off-by: Johannes Berg

    Marco Porsch