From: Florian Westphal <fw@strlen.de>
To: Subash Abhinov Kasiviswanathan <subashab@codeaurora.org>
Cc: netfilter-devel@vger.kernel.org, fw@strlen.de,
pablo@netfilter.org, Manoj Basapathi <manojbm@codeaurora.org>
Subject: Re: [PATCH nf-next] netfilter: xtables: Add snapshot of hardidletimer target
Date: Thu, 30 Jan 2020 13:44:19 +0100 [thread overview]
Message-ID: <20200130124419.GG795@breakpoint.cc> (raw)
In-Reply-To: <1580344627-2452-1-git-send-email-subashab@codeaurora.org>
Subash Abhinov Kasiviswanathan <subashab@codeaurora.org> wrote:
> From: Manoj Basapathi <manojbm@codeaurora.org>
>
> This is a snapshot of hardidletimer netfilter target.
>
> This patch implements a hardidletimer Xtables target that can be
> used to identify when interfaces have been idle for a certain period
> of time.
>
> Timers are identified by labels and are created when a rule is set
> with a new label. The rules also take a timeout value (in seconds) as
> an option. If more than one rule uses the same timer label, the timer
> will be restarted whenever any of the rules get a hit.
>
> One entry for each timer is created in sysfs. This attribute contains
> the timer remaining for the timer to expire. The attributes are
> located under the xt_idletimer class:
>
> /sys/class/xt_hardidletimer/timers/<label>
>
> When the timer expires, the target module sends a sysfs notification
> to the userspace, which can then decide what to do (eg. disconnect to
> save power)
>
> Compared to IDLETIMER, HARDIDLETIMER can send notifications when
> CPU is in suspend too, to notify the timer expiry.
>
> v1->v2: Moved all functionality into IDLETIMER module to avoid
> code duplication per comment from Florian.
>
> Signed-off-by: Manoj Basapathi <manojbm@codeaurora.org>
> Signed-off-by: Subash Abhinov Kasiviswanathan <subashab@codeaurora.org>
> ---
> include/uapi/linux/netfilter/xt_IDLETIMER.h | 3 +
> net/netfilter/xt_IDLETIMER.c | 85 ++++++++++++++++++++++++++---
> 2 files changed, 79 insertions(+), 9 deletions(-)
>
> diff --git a/include/uapi/linux/netfilter/xt_IDLETIMER.h b/include/uapi/linux/netfilter/xt_IDLETIMER.h
> index 3c586a1..10a40bb 100644
> --- a/include/uapi/linux/netfilter/xt_IDLETIMER.h
> +++ b/include/uapi/linux/netfilter/xt_IDLETIMER.h
> @@ -33,12 +33,15 @@
> #include <linux/types.h>
>
> #define MAX_IDLETIMER_LABEL_SIZE 28
> +#define XT_IDLETIMER_ALARM 0x01
>
> struct idletimer_tg_info {
> __u32 timeout;
>
> char label[MAX_IDLETIMER_LABEL_SIZE];
>
> + __u8 timer_type;
> +
This breaks binary abi of idletimer_tg_info.
You will need to add a new target revision for this, i.e.
struct idletimer_tg_info_v1.
See net/netfilter/xt_CT.c for an example target that has
several revisions.
prev parent reply other threads:[~2020-01-30 12:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-30 0:37 [PATCH nf-next] netfilter: xtables: Add snapshot of hardidletimer target Subash Abhinov Kasiviswanathan
2020-01-30 12:44 ` Florian Westphal [this message]
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=20200130124419.GG795@breakpoint.cc \
--to=fw@strlen.de \
--cc=manojbm@codeaurora.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=subashab@codeaurora.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.