mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Nikita Popov <nikita.ppv@gmail.com>
To: musl@lists.openwall.com
Subject: [musl] strftime %Z behavior with manually populated struct tm
Date: Mon, 10 Aug 2020 15:31:23 +0200	[thread overview]
Message-ID: <CAF+90c_-2vW-HfO74U68KDwWTc9_mpK9ZhH+tu_tnMLWVkTPGw@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1084 bytes --]

Hi,

Currently, strftime() %Z will print an empty string if the provided tm_zone
does not originate from musl. It appears that this behavior is explicitly
implemented in __tm_to_tzname(). Would it be possible to instead print any
non-NULL tm_zone as provided?

For consumers manually populating the struct tm structure, it is
non-trivial to work around the current behavior. Python introduced a work
around in
https://github.com/python/cpython/commit/163eca34c48f1b25e1504e37f4656773fd0fdc78,
but it is not easy to generalize.

From what I gathered, the original concern here was that a consumer
manually initializing struct tm may not initialize the tm_zone field. As
struct tm is only specified to contain "at least" certain members, manual
initialization of this structure is already on shaky ground anyway and I
think it is more useful to assume the initialization is correct than try to
deal with garbage data. Because other libc implementation do not try to
validate the pointer either (beyond being non-NULL), incorrect
initialization is unlikely in practice.

Regards,
Nikita

[-- Attachment #2: Type: text/html, Size: 2154 bytes --]

             reply	other threads:[~2020-08-10 13:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-10 13:31 Nikita Popov [this message]
2020-08-10 16:53 ` Rich Felker
2020-08-12 12:57 ` [musl] " Nikita Popov
2020-08-12 14:05   ` Nikita Popov
2020-08-12 15:17   ` 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=CAF+90c_-2vW-HfO74U68KDwWTc9_mpK9ZhH+tu_tnMLWVkTPGw@mail.gmail.com \
    --to=nikita.ppv@gmail.com \
    --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).