From: Jozsef Kadlecsik <kadlec@netfilter.org>
To: Neutron Soutmun <neo.neutron@gmail.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH] ipset: fix print format warning
Date: Tue, 19 Jan 2021 09:01:21 +0100 (CET) [thread overview]
Message-ID: <78385ce0-e237-4281-476e-b21e33a6169@netfilter.org> (raw)
In-Reply-To: <YAUVdnEg6OMPsUet@hydrogen>
Hi,
On Mon, 18 Jan 2021, Neutron Soutmun wrote:
> * Use PRIx64 for portablility over various architectures.
> * The format string for the 64bit number printing is incorrect,
> the `%` sign is missing.
> * The force types casting over the uint32_t and uint64_t are unnecessary
> which warned by the compiler on different architecture.
>
> Signed-off-by: Neutron Soutmun <neo.neutron@gmail.com>
Thanks, patch is applied in the ipset git tree.
Best regards,
Jozsef
> ---
> lib/print.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/lib/print.c b/lib/print.c
> index 0d86a98..a7ffd81 100644
> --- a/lib/print.c
> +++ b/lib/print.c
> @@ -431,10 +431,10 @@ ipset_print_hexnumber(char *buf, unsigned int len,
> *(const uint16_t *) number);
> else if (maxsize == sizeof(uint32_t))
> return snprintf(buf, len, "0x%08"PRIx32,
> - (long unsigned) *(const uint32_t *) number);
> + *(const uint32_t *) number);
> else if (maxsize == sizeof(uint64_t))
> - return snprintf(buf, len, "0x016lx",
> - (long long unsigned) *(const uint64_t *) number);
> + return snprintf(buf, len, "0x%016"PRIx64,
> + *(const uint64_t *) number);
> else
> assert(0);
> return 0;
> --
> 2.30.0
>
-
E-mail : kadlec@blackhole.kfki.hu, kadlecsik.jozsef@wigner.hu
PGP key : https://wigner.hu/~kadlec/pgp_public_key.txt
Address : Wigner Research Centre for Physics
H-1525 Budapest 114, POB. 49, Hungary
prev parent reply other threads:[~2021-01-19 8:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-18 4:58 [PATCH] ipset: fix print format warning Neutron Soutmun
2021-01-19 8:01 ` Jozsef Kadlecsik [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=78385ce0-e237-4281-476e-b21e33a6169@netfilter.org \
--to=kadlec@netfilter.org \
--cc=neo.neutron@gmail.com \
--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.