netdev - sysfs question

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-next>] [day] [month] [year] [list]

Message-ID: <20091112103940.GC322@e-circ.dyndns.org>
Date:	Thu, 12 Nov 2009 11:39:41 +0100
From:	Kurt Van Dijck <kurt.van.dijck@....be>
To:	Wolfgang Grandegger <wg@...ndegger.com>
Cc:	netdev@...r.kernel.org
Subject: sysfs question

Hi,

Within the socketcan project, we came into a situation that
might benefit with input from the netdev mailing list.

The main issue is the policy to add sysfs properties in
/sys/class/net/canX.

The reason for this is that cards (devices) with multiple network
interfaces may require properties per network.

An obvious property would be the 'channel number of the card'. Other
properties could be things like type of output circuitry, ..., rather
hardware specific.

I see currently 3 options:
1) such properties in /sys/class/net/canX would be allowed.
2) such properties would belong in /sys/class/net/canX/<subdirectory tbd>/
3) such properties would go somewhere else.

Some input with regard to sysfs policies would be helpfull.

Kurt
--
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