summaryrefslogtreecommitdiff
path: root/.clang-format
diff options
context:
space:
mode:
authorMarian Postevca <posteuca@mutex.one>2021-12-05 00:49:12 +0300
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2021-12-13 17:22:23 +0300
commit890d5b40908bfd1a79be018d2d297cf9df60f4ee (patch)
tree0bb6ae5ee41a20787c37fb7653aa0443ebb9919f /.clang-format
parent2585cf9dfaaddf00b069673f27bb3f8530e2039c (diff)
downloadlinux-890d5b40908bfd1a79be018d2d297cf9df60f4ee.tar.xz
usb: gadget: u_ether: fix race in setting MAC address in setup phase
When listening for notifications through netlink of a new interface being registered, sporadically, it is possible for the MAC to be read as zero. The zero MAC address lasts a short period of time and then switches to a valid random MAC address. This causes problems for netd in Android, which assumes that the interface is malfunctioning and will not use it. In the good case we get this log: InterfaceController::getCfg() ifName usb0 hwAddr 92:a8:f0:73:79:5b ipv4Addr 0.0.0.0 flags 0x1002 In the error case we get these logs: InterfaceController::getCfg() ifName usb0 hwAddr 00:00:00:00:00:00 ipv4Addr 0.0.0.0 flags 0x1002 netd : interfaceGetCfg("usb0") netd : interfaceSetCfg() -> ServiceSpecificException (99, "[Cannot assign requested address] : ioctl() failed") The reason for the issue is the order in which the interface is setup, it is first registered through register_netdev() and after the MAC address is set. Fixed by first setting the MAC address of the net_device and after that calling register_netdev(). Fixes: bcd4a1c40bee885e ("usb: gadget: u_ether: construct with default values and add setters/getters") Cc: stable@vger.kernel.org Signed-off-by: Marian Postevca <posteuca@mutex.one> Link: https://lore.kernel.org/r/20211204214912.17627-1-posteuca@mutex.one Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to '.clang-format')
0 files changed, 0 insertions, 0 deletions