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
| ||
|
Message-ID: <774a8092-c677-4942-9a0a-9a42ea5ca1fd@suse.com> Date: Thu, 16 Nov 2023 14:02:47 +0100 From: Oliver Neukum <oneukum@...e.com> To: Bjørn Mork <bjorn@...k.no>, Oliver Neukum <oneukum@...e.com> Cc: netdev@...r.kernel.org Subject: Re: [RFC] usbnet: assign unique random MAC On 16.11.23 13:39, Bjørn Mork wrote: > Oliver Neukum <oneukum@...e.com> writes: > >> A module parameter to go back to the old behavior >> is included. > > Is this really required? If we add it now then we can never get rid of > it. Why not try without, and add this back if/when somebody complains > about the new behaviour? > > I believe there's a fair chance no one will notice or complain. And we > have much cleaner code and one module param less. Isn't it a bit evil to change behavior? Do you think I should make a different version for stable with the logic for retaining the old behavior inverted? Regards Oliver
Powered by blists - more mailing lists