[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LSU.2.01.1006022127430.32028@obet.zrqbmnf.qr>
Date: Wed, 2 Jun 2010 21:29:10 +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 Wednesday 2010-06-02 21:05, Luciano Coelho wrote:
>> > >+ idletimer_tg_kobj = kobject_create_and_add("idletimer",
>> > >+ &THIS_MODULE->mkobj.kobj);
>> >
>> > Isn't this going to oops when you compile this module as =y?
>>
>> Damn, that's true. :(
>>
>> I'll investigate how to fix this.
>
>Would it be too hacky to force it to be a module (ie. add "depends on m"
>in Kconfig)?
>
>Besides /sys/module/xt_IDLETIMER and /sys/class/net, which we have
>already discarded, I can't find any other place that would make sense to
>add the idletimer in the kernel object hierarchy...
While THIS_MODULE is NULL in =y mode, /sys/module/<xyz> can still exist
(cf. /sys/module/printk). I just don't know how to get at the kobj for
it, but the existence of it must mean it's there somewhere. Might ask
sysfs authors.
--
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