Re: [PATCH v3] netfilter: Xtables: idletimer target implementation

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Patrick McHardy
Date: Wednesday, June 9, 2010 - 6:45 am

luciano.coelho@nokia.com wrote:

Basically this seems fine to me, some minor comments below.


This seems a bit generic, maybe better use MAX_IDLETIMER_LABER_SIZE.


How does this work with multiple namespaces? It seems every namespace
can bind to any timer.


time_after()?


The only caller is the target cleanup function, why don't you just move
everything there?


sizeof(*attr)


Better fully set up the timer before activating it.


list_for_each_entry_safe(). This function seems unnecessary though, the
module
can't be unloaded while its still in use and cleanup will already happen
when the
rules are removed.


You need BH protection here as well for the output path.


!info->label is impossible. You should check for \0 termination instead.

spin_lock_bh()


How does this prevent creating the same timer twice?


--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Re: [PATCH v3] netfilter: Xtables: idletimer target implem ..., Patrick McHardy, (Wed Jun 9, 6:45 am)