From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Ander Juaristi <a@juaristi.eus>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH v4 2/2] netfilter: nft_meta: support for time matching
Date: Tue, 13 Aug 2019 21:10:04 +0200 [thread overview]
Message-ID: <20190813191004.jltzdpmcagp443pm@salvia> (raw)
In-Reply-To: <20190813183820.6659-2-a@juaristi.eus>
Just a few nitpicks and we go :-)
On Tue, Aug 13, 2019 at 08:38:20PM +0200, Ander Juaristi wrote:
> diff --git a/include/uapi/linux/netfilter/nf_tables.h b/include/uapi/linux/netfilter/nf_tables.h
> index 82abaa183fc3..67ae55e08518 100644
> --- a/include/uapi/linux/netfilter/nf_tables.h
> +++ b/include/uapi/linux/netfilter/nf_tables.h
> @@ -799,6 +799,9 @@ enum nft_exthdr_attributes {
> * @NFT_META_OIFKIND: packet output interface kind name (dev->rtnl_link_ops->kind)
> * @NFT_META_BRI_IIFPVID: packet input bridge port pvid
> * @NFT_META_BRI_IIFVPROTO: packet input bridge vlan proto
> + * @NFT_META_TIME: a UNIX timestamp
* @NFT_META_TIME: time since 1970 (in nanoseconds)
Probably rename this to NFT_META_TIME_NS I'd suggest.
> + * @NFT_META_TIME_DAY: day of week
+ * @NFT_META_TIME_DAY: day of week (from 0 = Sunday to 6 = Saturday)
> + * @NFT_META_TIME_HOUR: hour of day
+ * @NFT_META_TIME_HOUR: hour of the day (in seconds)
> */
> enum nft_meta_keys {
> NFT_META_LEN,
> @@ -831,6 +834,9 @@ enum nft_meta_keys {
> NFT_META_OIFKIND,
> NFT_META_BRI_IIFPVID,
> NFT_META_BRI_IIFVPROTO,
> + NFT_META_TIME,
> + NFT_META_TIME_DAY,
> + NFT_META_TIME_HOUR,
> };
>
> /**
> diff --git a/net/netfilter/nft_meta.c b/net/netfilter/nft_meta.c
> index f1b1d948c07b..3e665a1a744a 100644
> --- a/net/netfilter/nft_meta.c
> +++ b/net/netfilter/nft_meta.c
> @@ -28,6 +28,27 @@
>
> static DEFINE_PER_CPU(struct rnd_state, nft_prandom_state);
Probably a few constant definitions to be used in nft_meta_weekday().
#define NFT_NETA_SECS_PER_MINUTE 60
#define NFT_META_SECS_PER_HOUR 3600
#define NFT_META_SECS_PER_DAY 86400
#define NFT_META_DAYS_PER_WEEK 7
these numbers are easy to guess, but this helps along time to read
this code.
> +static u8 nft_meta_weekday(unsigned long secs)
> +{
> + u8 wday;
> + unsigned int dse;
Reverse definition, from longest to shortest line:
unsigned int dse;
u8 wday;
> + secs -= 60 * sys_tz.tz_minuteswest;
> + dse = secs / 86400;
> + wday = (4 + dse) % 7;
> +
> + return wday;
> +}
> +
> +static u32 nft_meta_hour(unsigned long secs)
> +{
> + struct tm tm;
> +
> + time64_to_tm(secs, 0, &tm);
> +
> + return tm.tm_hour * 3600 + tm.tm_min * 60 + tm.tm_sec;
> +}
> +
> void nft_meta_get_eval(const struct nft_expr *expr,
> struct nft_regs *regs,
> const struct nft_pktinfo *pkt)
> @@ -226,6 +247,15 @@ void nft_meta_get_eval(const struct nft_expr *expr,
> goto err;
> strncpy((char *)dest, out->rtnl_link_ops->kind, IFNAMSIZ);
> break;
> + case NFT_META_TIME:
> + nft_reg_store64(dest, ktime_get_real_ns());
> + break;
> + case NFT_META_TIME_DAY:
> + nft_reg_store8(dest, nft_meta_weekday(get_seconds()));
> + break;
> + case NFT_META_TIME_HOUR:
> + *dest = nft_meta_hour(get_seconds());
> + break;
> default:
> WARN_ON(1);
> goto err;
> @@ -338,6 +368,15 @@ int nft_meta_get_init(const struct nft_ctx *ctx,
> len = sizeof(u8);
> break;
> #endif
> + case NFT_META_TIME:
> + len = sizeof(u64);
> + break;
> + case NFT_META_TIME_DAY:
> + len = sizeof(u8);
> + break;
> + case NFT_META_TIME_HOUR:
> + len = sizeof(u32);
> + break;
> default:
> return -EOPNOTSUPP;
> }
> --
> 2.17.1
>
next prev parent reply other threads:[~2019-08-13 19:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-13 18:38 [PATCH v4 1/2] netfilter: Introduce new 64-bit helper functions Ander Juaristi
2019-08-13 18:38 ` [PATCH v4 2/2] netfilter: nft_meta: support for time matching Ander Juaristi
2019-08-13 19:10 ` Pablo Neira Ayuso [this message]
2019-08-13 19:14 ` Florian Westphal
2019-08-13 19:15 ` Florian Westphal
2019-08-13 18:58 ` [PATCH v4 1/2] netfilter: Introduce new 64-bit helper functions Pablo Neira Ayuso
2019-08-15 9:46 ` Ander Juaristi
2019-08-15 9:56 ` Pablo Neira Ayuso
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=20190813191004.jltzdpmcagp443pm@salvia \
--to=pablo@netfilter.org \
--cc=a@juaristi.eus \
--cc=netfilter-devel@vger.kernel.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 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).