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

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

Date:	Sat, 08 Dec 2007 00:04:29 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	herbert@...dor.apana.org.au
CC:	netdev@...r.kernel.org, yoshifuji@...ux-ipv6.org
Subject: 'default' vs. 'all'

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.

The question is how to implement this nicely.

What do you think?
--
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