netdev - Re: [RFC 1/1] net: move IFF_LIVE_ADDR

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 10:59:17 -0700
From:   Stephen Hemminger <stephen@...workplumber.org>
To:     James Prestwood <prestwoj@...il.com>
Cc:     netdev@...r.kernel.org
Subject: Re: [RFC 1/1] net: move IFF_LIVE_ADDR_CHANGE to public flag

On Thu,  4 Aug 2022 10:43:07 -0700
James Prestwood <prestwoj@...il.com> wrote:

> + * @IFF_LIVE_ADDR_CHANGE: device supports hardware address
> + *	change when it's running. Volatile

Since this is a property of the device driver, why is it volatile?

When you make it part of uapi, you also want to restrict userspace
from changing the value via sysfs?