From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Lukas Straub <lukasstraub2@web.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH nft] meta time: use uint64_t instead of time_t
Date: Tue, 5 Apr 2022 13:58:24 +0200 [thread overview]
Message-ID: <Ykwu4PnorVaAG1Op@salvia> (raw)
In-Reply-To: <20220405101026.867817071@web.de>
On Tue, Apr 05, 2022 at 10:41:14AM +0000, Lukas Straub wrote:
> time_t may be 32 bit on some platforms and thus can't fit a timestamp
> with nanoseconds resolution. This causes overflows and ultimatively
> breaks meta time expressions on such platforms.
>
> Fix this by using uint64_t instead.
Applied, thanks
next prev parent reply other threads:[~2022-04-05 14:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220405101016.855221490@web.de>
2022-04-05 10:41 ` [PATCH nft] meta time: use uint64_t instead of time_t Lukas Straub
2022-04-05 11:58 ` Pablo Neira Ayuso [this message]
2022-04-05 13:28 ` Phil Sutter
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=Ykwu4PnorVaAG1Op@salvia \
--to=pablo@netfilter.org \
--cc=lukasstraub2@web.de \
--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 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.