public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH v2 7/7] misc: syslog: Use RFC5424
Date: Fri, 18 Feb 2022 19:50:57 -0800	[thread overview]
Message-ID: <a6c37746-9aaa-480b-0434-bb484c4c82da@cs.ucla.edu> (raw)
In-Reply-To: <20220218142322.432304-8-adhemerval.zanella@linaro.org>

There should be documentation about the change, somewhere.

On 2/18/22 06:23, Adhemerval Zanella via Libc-alpha wrote:

> +  struct tm *gmtm = __gmtime64_r (&ts.tv_sec, &now_tm);
> +  if (gmtm == NULL)
> +    strcpy (timebuf->b, NILVALUE);

RFC 5424 requires unsigned four-digit years, so change "gmtm == NULL" to 
"gmtm == NULL || ! (-1900 <= gmtm->tm_year && gmtm->tm_year <= 9999 - 
1900)". Or, if the idea is to depart from RFC 5424 for out-of-range 
years (which might be better), document the departure.

> +  else
> +    {
> +      size_t datebytes = __strftime_l (timebuf->b, sizeof timebuf->b,
> +				       "%FT%T", gmtm, _nl_C_locobj_ptr);
RFC 5424 does not allow leap seconds, so something like this:

     if (gmtm->tv_sec == 60)
       {
          gmtm->tv_sec = 59;
          gmtm->tv_nsec = 999999999;
       }

before calling __strftime_l. (Or again, if the idea is to depart from 
RFC 5424, document the departure.)

> +      int usec = ts.tv_nsec / 1000;

Typically fewer instructions (and still correct) if you replace 1000 
with 1000ul (admittedly a microoptimization....).

  reply	other threads:[~2022-02-19  3:50 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-18 14:23 [PATCH v2 0/7] Use RFC5424 for syslog Adhemerval Zanella
2022-02-18 14:23 ` [PATCH v2 1/7] support: Add xmkfifo Adhemerval Zanella
2022-02-18 14:23 ` [PATCH v2 2/7] misc: Add syslog test Adhemerval Zanella
2022-02-18 14:23 ` [PATCH v2 3/7] misc: syslog: Fix indentation and style Adhemerval Zanella
2022-02-18 14:23 ` [PATCH v2 4/7] misc: syslog: Simplify implementation Adhemerval Zanella
2022-02-19  3:15   ` Paul Eggert
2022-02-21 13:15     ` Adhemerval Zanella
2022-02-21 22:25       ` Paul Eggert
2022-02-21 14:06     ` Andreas Schwab
2022-02-21 22:23       ` Paul Eggert
2022-02-18 14:23 ` [PATCH v2 5/7] misc: syslog: Use static buffer Adhemerval Zanella
2022-02-19  3:45   ` Paul Eggert
2022-02-21 13:31     ` Adhemerval Zanella
2022-02-18 14:23 ` [PATCH v2 6/7] misc: syslog: Move SYSLOG_NAME to USE_MISC (BZ #16355) Adhemerval Zanella
2022-02-18 14:23 ` [PATCH v2 7/7] misc: syslog: Use RFC5424 Adhemerval Zanella
2022-02-19  3:50   ` Paul Eggert [this message]
2022-02-21 14:01     ` Adhemerval Zanella
2022-02-21 16:18       ` Adhemerval Zanella
2022-02-21 22:25         ` Paul Eggert
2022-02-19 20:35   ` Dan Raymond
2022-02-19 22:23     ` Paul Eggert

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=a6c37746-9aaa-480b-0434-bb484c4c82da@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=adhemerval.zanella@linaro.org \
    --cc=libc-alpha@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).