| 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
| ||
|
Date: Thu, 3 Jun 2010 09:58:27 +0200 (CEST) From: Jan Engelhardt <jengelh@...ozas.de> To: Luciano Coelho <luciano.coelho@...ia.com> cc: "netdev@...r.kernel.org" <netdev@...r.kernel.org>, "netfilter-devel@...r.kernel.org" <netfilter-devel@...r.kernel.org>, "kaber@...sh.net" <kaber@...sh.net>, Timo Teras <timo.teras@....fi> Subject: Re: [PATCH v2] netfilter: Xtables: idletimer target implementation On Thursday 2010-06-03 09:04, Luciano Coelho wrote: > >Looking closer, it seems that it makes a bit of sense to add a kernel >module to /sys/device/system. I think it makes more sense than adding >to the module class or to the net class, actually. The idletimer is not >a net device (so it doesn't fit in /sys/class/net) and it is not a >module, even though it may be handled by the xt_IDLETIMER module. > >So we can look at the xt_idletimer as a system device, which is not a >peripheral device in itself, but a software timer device (there are >already similar components). > >I'll add the kernel object we need as a system class device, so it will >go under /sys/devices/system/xt_idletimer. Does that make sense to you? Mh.. somehow I'd pick /sys/devices/virtual/xt_idletimer. Or even create a /sys/net/xt_idletimer. (/sys has conceptual subsystems directly beneath it: devices, fs, kernel, ...) -- 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
Powered by blists - more mailing lists