netdev - Re: 'default' vs. 'all'

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:	Sat, 08 Dec 2007 00:14:11 -0800 (PST)
From:	YOSHIFUJI Hideaki / 吉藤英明 
	<yoshfuji@...ux-ipv6.org>
To:	davem@...emloft.net
Cc:	herbert@...dor.apana.org.au, netdev@...r.kernel.org,
	yoshfuji@...ux-ipv6.org
Subject: Re: 'default' vs. 'all'

In article <20071208.000429.66028544.davem@...emloft.net> (at Sat, 08 Dec 2007 00:04:29 -0800 (PST)), David Miller <davem@...emloft.net> says:

> Herbert, Yoshifuji and I were just discussing the
> sysfs device attribute issue.
> 
> It's seems sane to me that if we had some kind of
> 'dirty' bit per attribute we could propagate default
> settings everywhere except where the dirty bit had
> been set.

One good event to propagate is the NETDEV_UP; if the dirty bit is
not set when the device is brought up, copy the default values to
the device.

Regards,

--yoshfuji @ Seattle
--
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