From: Luciano Coelho <luciano.coelho@nokia.com>
To: ext Jan Engelhardt <jengelh@medozas.de>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"netfilter-devel@vger.kernel.org"
<netfilter-devel@vger.kernel.org>,
"kaber@trash.net" <kaber@trash.net>,
Timo Teras <timo.teras@iki.fi>
Subject: Re: [PATCH v2] netfilter: Xtables: idletimer target implementation
Date: Wed, 02 Jun 2010 22:05:53 +0300 [thread overview]
Message-ID: <1275505553.2797.2.camel@powerslave> (raw)
In-Reply-To: <1275503835.1574.0.camel@powerslave>
On Wed, 2010-06-02 at 20:37 +0200, Coelho Luciano (Nokia-D/Helsinki)
wrote:
> On Wed, 2010-06-02 at 17:16 +0200, ext Jan Engelhardt wrote:
> > On Wednesday 2010-06-02 15:41, Luciano Coelho wrote:
> >
> > >+static int __init idletimer_tg_init(void)
> > >+{
> > >+ int ret;
> > >+
> > >+ 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...
--
Cheers,
Luca.
next prev parent reply other threads:[~2010-06-02 19:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-02 13:41 [PATCH v2] netfilter: Xtables: idletimer target implementation Luciano Coelho
2010-06-02 15:16 ` Jan Engelhardt
2010-06-02 18:37 ` Luciano Coelho
2010-06-02 19:05 ` Luciano Coelho [this message]
2010-06-02 19:29 ` Jan Engelhardt
2010-06-02 19:52 ` Luciano Coelho
2010-06-02 20:04 ` Luciano Coelho
2010-06-02 21:01 ` Luciano Coelho
2010-06-03 7:04 ` Luciano Coelho
2010-06-03 7:58 ` Jan Engelhardt
2010-06-03 10:13 ` Luciano Coelho
2010-06-03 13:17 ` Luciano Coelho
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1275505553.2797.2.camel@powerslave \
--to=luciano.coelho@nokia.com \
--cc=jengelh@medozas.de \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=timo.teras@iki.fi \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).