linux-kernel - PROBLEM: No static MAC address for usb gadget ethernet via kernel parameter any more.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:   Thu, 12 May 2022 15:38:47 +0200
From:   Maximilian Senftleben <kernel@...l.msdigital.de>
To:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:     linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org,
        Marian Postevca <posteuca@...ex.one>
Subject: PROBLEM: No static MAC address for usb gadget ethernet via kernel
 parameter any more.

[1.] One line summary of the problem:

No static MAC address for usb gadget ethernet via kernel boot parameter 
any more.

[2.] Full description of the problem/report:

In 5.15. and before we were able to set a static MAC address for the usb 
gadget ethernet connection using kernel parameters "g_ether.dev_addr" 
and "g_ether.host_addr".
Since 5.16. and more concrete after commit 
890d5b40908bfd1a79be018d2d297cf9df60f4ee, this is no longer possible, 
and a random MAC address is assigned.
(Possible Regression)

[3.] Keywords (i.e., modules, networking, kernel):
usb, gadget, mac, g_ether

[4.] Kernel information
[4.1.] Kernel version (from /proc/version):
Linux version 5.17.4-141174-ge11818a6ec02 (ms@...al) 
(arm-v7a-linux-gnueabihf-gcc (OSELAS.Toolchain-2020.08.0 10-20200822) 
10.2.1 20200822, GNU ld (GNU Binutils) 2.35) #14 SMP Thu May 12 13:51:50 
CEST 2022
[4.2.] Kernel .config file:
-

[5.] Most recent kernel version which did not have the bug:
5.15

[6.] Output of Oops.. message (if applicable) with symbolic information 
resolved (see Documentation/admin-guide/bug-hunting.rst)
-

[7.] A small shell script or example program which triggers the problem 
(if possible)
-

[8.] Environment
-

[9.] Other notes, patches, fixes, workarounds:

In 5.17.4 reverting said commit 890d5b40908bfd1a79be018d2d297cf9df60f4ee 
did resolve the issue for me.