netdev - value of dev->addr_assign

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20121224094730.GB1559@minipsycho.orion>
Date:	Mon, 24 Dec 2012 10:47:30 +0100
From:	Jiri Pirko <jiri@...nulli.us>
To:	netdev@...r.kernel.org
Cc:	sassmann@...hat.com
Subject: value of dev->addr_assign_type

Hi Stefan/all.

Looking at possible values of dev->addr_assign_type I found out:

/* hardware address assignment types */
#define NET_ADDR_PERM          0       /* address is permanent (default) */
#define NET_ADDR_RANDOM                1       /* address is generated randomly */
#define NET_ADDR_STOLEN                2       /* address is stolen from other device */

By this it looks like dev->addr_assign_type value is always one of these 3.

But by the way the value is treated in dev_hw_addr_random() for example:
dev->addr_assign_type |= NET_ADDR_RANDOM;
It looks like NET_ADDR_* ought to be flags...

That confuses me.

Jiri

ps.: introduced in c1f79426e2df5ef96fe3e76de6c7606d15bf390b
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html