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-prev] [thread-next>] [day] [month] [year] [list]
Date:   Thu, 4 Aug 2022 22:49:51 +0200
From:   Andrew Lunn <andrew@...n.ch>
To:     James Prestwood <prestwoj@...il.com>
Cc:     netdev@...r.kernel.org
Subject: Re: [RFC 0/1] Move IFF_LIVE_ADDR_CHANGE to public flag

>   net: move IFF_LIVE_ADDR_CHANGE to public flag

If this concept is accepted, i would actually change the flag name a
little. That will help developers know the semantics of the flag have
changed when their code fails to compile. Maybe make the public flag
IFF_ADDR_CHANGE_LIVE?

	Andrew

Powered by blists - more mailing lists