mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: [PATCH] strftime: fix %z sign for small negative time zone offsets
Date: Thu, 2 Aug 2018 19:29:23 -0400	[thread overview]
Message-ID: <20180802232923.GO1392@brightrain.aerifal.cx> (raw)
In-Reply-To: <20180725101142.29159-1-zajec5@gmail.com>

On Wed, Jul 25, 2018 at 12:11:42PM +0200, Rafał Miłecki wrote:
> From: Rafał Miłecki <rafal@milecki.pl>
> 
> Using + printf flag for printing plus/minus sign isn't reliable for
> negative offsets greater than -3600. In such cases the first two digits
> are zero but offset still should be printed with a leading minus char.
> 
> Existing implementation results in code:
> 	struct tm tm = { .tm_gmtoff = -1800, };
> 	char buf[255];
> 	strftime(buf, sizeof(buf), "%z", &tm);
> 	puts(buf);
> printing +0030 instead of -0030.
> 
> This patch fixes it by handling sign character manually and checking the
> __tm_gmtoff value (instead of __tm_gmtoff / 3600).
> 
> Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
> ---
>  src/time/strftime.c | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/src/time/strftime.c b/src/time/strftime.c
> index 0a256970..6716ad4b 100644
> --- a/src/time/strftime.c
> +++ b/src/time/strftime.c
> @@ -181,7 +181,8 @@ const char *__strftime_fmt_1(char (*s)[100], size_t *l, int f, const struct tm *
>  			*l = 0;
>  			return "";
>  		}
> -		*l = snprintf(*s, sizeof *s, "%+.2ld%.2d",
> +		*l = snprintf(*s, sizeof *s, "%c%.2ld%.2d",
> +			tm->__tm_gmtoff >= 0 ? '+' : '-',
>  			(tm->__tm_gmtoff)/3600,
>  			abs(tm->__tm_gmtoff%3600)/60);
>  		return *s;
> -- 

I think this is incorrect. tm->__tm_gmtoff/3600 can still be negative,
and then the - sign is printed twice.

I suspect your patch is correct if we add abs() around that expression
too, but maybe it makes more sense to assemble the value to be printed
as a single integer:

	tm->__tm_gmtoff/3600*100 + tm->__tm_gmtoff%3600/60

I didn't spend a lot of time working out that this is correct, but it
looks right and checks out with a few test cases.

Rich


  reply	other threads:[~2018-08-02 23:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-25 10:11 Rafał Miłecki
2018-08-02 23:29 ` Rich Felker [this message]
2018-08-02 23:31   ` Rich Felker
2018-08-08  2:14   ` Rich Felker

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=20180802232923.GO1392@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --cc=musl@lists.openwall.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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).