From: Willy Tarreau <w@1wt.eu>
To: david.laight.linux@gmail.com
Cc: "Thomas Weißschuh" <linux@weissschuh.net>,
linux-kernel@vger.kernel.org, "Cheng Li" <lechain@gmail.com>
Subject: Re: [PATCH v2 next 07/11] tools/nolibc/printf: Add support for conversion flags "#- +" and format "%X"
Date: Sun, 8 Feb 2026 16:47:23 +0100 [thread overview]
Message-ID: <aYiwC6Fa2oSlmGBp@1wt.eu> (raw)
In-Reply-To: <20260206191121.3602-8-david.laight.linux@gmail.com>
On Fri, Feb 06, 2026 at 07:11:17PM +0000, david.laight.linux@gmail.com wrote:
> -/* simple printf(). It supports the following formats:
> - * - %[-][width][{l,t,z,ll,L,j,q}]{d,u,c,x,p,s,m,%}
> - * - %%
> - * - invalid formats are copied to the output buffer
> +/* printf(). Supports most of the normal integer and string formats.
> + * - %[#-+ ][width][{l,t,z,ll,L,j,q}]{d,i,u,c,x,X,p,s,m,%}
> + * - %% generates a single %
> + * - %m outputs strerror(errno).
> + * - # only affects %x and prepends 0x to non-zero values.
> + * - %o (octal) isn't supported.
> + * - %X outputs a..f the same as %x.
> + * - No support for zero padding, precision or variable widths.
> + * - No support for wide characters.
> + * - invalid formats are copied to the output buffer.
> */
Thanks for updating this one, it does help quite a bit.
> /* This code uses 'flag' variables that are indexed by the low 6 bits
> @@ -279,7 +285,7 @@ int __nolibc_printf(__nolibc_printf_cb cb, void *state, const char *fmt, va_list
> unsigned int written, width;
> unsigned int flags, ch_flag;
> size_t len;
> - char tmpbuf[21];
> + char tmpbuf[32 + 24];
The previous buffer was sized to store a 64-bit int. I couldn't figure
what these 32 and 24 correspond to with the new supported specifiers.
Maybe please add a short comment on the line to hint about what they
correspond to ?
> const char *outstr;
>
> written = 0;
> @@ -334,19 +340,32 @@ int __nolibc_printf(__nolibc_printf_cb cb, void *state, const char *fmt, va_list
>
> /* Conversion specifiers. */
>
> - /* Numeric conversion specifiers. */
> - ch_flag = _NOLIBC_PF_CHAR_IS_ONE_OF(ch, 'c', 'd', 'i', 'u', 'x', 'p');
> - if (ch_flag != 0) {
> + /* Numeric and pointer conversion specifiers.
> + *
> + * Use an explicit bound check (rather than _NOLIBC_PF_CHAR_IS_ONE_OF())
> + * so that 'X' can be allowed through.
> + * 'X' gets treated and 'x' because _NOLIBC_PF_FLAG() returns the same
> + * value for both.
> + */
> + if ((ch < 'a' || ch > 'z') && ch != 'X')
> + goto non_numeric_conversion;
> +
> + /* We need to check for "%p" or "%#x" later, merging here gives better code.
> + * But '#' collides with 'c' so shift right.
> + */
> + ch_flag = _NOLIBC_PF_FLAG(ch) | (flags & _NOLIBC_PF_FLAG('#')) >> 1;
> + if (_NOLIBC_PF_FLAGS_CONTAIN(ch_flag, 'c', 'd', 'i', 'u', 'x', 'p', 's')) {
> unsigned long long v;
> long long signed_v;
> - char *out = tmpbuf;
> + char *out = tmpbuf + 32;
OK so you seem to be reserving a part of the buffer for certain uses ?
> + int sign = 0;
>
> /* 'long' is needed for pointer/string conversions and ltz lengths.
> * A single test can be used provided 'p' (the same bit as '0')
> * is masked from flags.
> */
> if (_NOLIBC_PF_FLAGS_CONTAIN(ch_flag | (flags & ~_NOLIBC_PF_FLAG('p')),
> - 'p', 'l', 't', 'z')) {
> + 'p', 's', 'l', 't', 'z')) {
> v = va_arg(args, unsigned long);
> signed_v = (long)v;
> } else if (_NOLIBC_PF_FLAGS_CONTAIN(flags, 'j', 'q')) {
> @@ -365,40 +384,62 @@ int __nolibc_printf(__nolibc_printf_cb cb, void *state, const char *fmt, va_list
> goto do_output;
> }
>
> + if (_NOLIBC_PF_FLAGS_CONTAIN(ch_flag, 's')) {
> + /* "%s" - character string. */
> + if (!v) {
> + outstr = "(null)";
> + len = 6;
> + goto do_output;
> + }
> + outstr = (void *)v;
> +do_strnlen_output:
> + len = strnlen(outstr, INT_MAX);
I get why you turned strlen() to strnlen(INT_MAX) (result being an int)
but this will not change anything IMHO in that the rest of a 2GB+ string
will be written in multiple passes and will overflow the output anyway.
Thus I think that sticking to strlen() remains simpler and less confusing.
(...)
> - else if (ch == 'm') {
> +
> +non_numeric_conversion:
> + if (ch == 'm') {
> #ifdef NOLIBC_IGNORE_ERRNO
> outstr = "unknown error";
> + len = __builtin_strlen(outstr);
> #else
> outstr = strerror(errno);
> + goto do_strnlen_output;
> #endif /* NOLIBC_IGNORE_ERRNO */
It's simlper (and smaller) to use the common label for both here:
#ifdef NOLIBC_IGNORE_ERRNO
outstr = "unknown error";
#else
outstr = strerror(errno);
#endif /* NOLIBC_IGNORE_ERRNO */
+ goto do_strnlen_output;
Overall OK to me.
Willy
next prev parent reply other threads:[~2026-02-08 15:47 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-06 19:11 [PATCH v2 next 00/11] tools/nolibc: Enhance printf() david.laight.linux
2026-02-06 19:11 ` [PATCH v2 next 01/11] tools/nolibc/printf: Change variable used for format chars from 'c' to 'ch' david.laight.linux
2026-02-07 18:51 ` Willy Tarreau
2026-02-16 18:52 ` Thomas Weißschuh
2026-02-06 19:11 ` [PATCH v2 next 02/11] tools/nolibc/printf: Move snprintf length check to callback david.laight.linux
2026-02-07 19:12 ` Willy Tarreau
2026-02-07 23:28 ` David Laight
2026-02-08 15:12 ` Willy Tarreau
2026-02-08 22:49 ` David Laight
2026-02-06 19:11 ` [PATCH v2 next 03/11] tools/nolibc/printf: Add buffering to vfprintf() callback david.laight.linux
2026-02-07 19:29 ` Willy Tarreau
2026-02-07 23:36 ` David Laight
2026-02-16 19:07 ` Thomas Weißschuh
2026-02-17 11:51 ` David Laight
2026-02-18 17:52 ` Thomas Weißschuh
2026-02-06 19:11 ` [PATCH v2 next 04/11] tools/nolibc/printf: Output pad characters in 16 byte chunks david.laight.linux
2026-02-07 19:38 ` Willy Tarreau
2026-02-07 23:43 ` David Laight
2026-02-08 15:14 ` Willy Tarreau
2026-02-16 19:30 ` Thomas Weißschuh
2026-02-16 22:29 ` David Laight
2026-02-18 17:30 ` Thomas Weißschuh
2026-02-06 19:11 ` [PATCH v2 next 05/11] tools/nolibc/printf: Simplify __nolibc_printf() david.laight.linux
2026-02-07 20:05 ` Willy Tarreau
2026-02-07 23:50 ` David Laight
2026-02-08 12:20 ` David Laight
2026-02-08 14:44 ` Willy Tarreau
2026-02-08 16:54 ` David Laight
2026-02-08 17:06 ` Willy Tarreau
2026-02-06 19:11 ` [PATCH v2 next 06/11] tools/nolibc/printf: Use bit-masks to hold requested flag, length and conversion chars david.laight.linux
2026-02-08 15:22 ` Willy Tarreau
2026-02-16 19:52 ` Thomas Weißschuh
2026-02-16 22:47 ` David Laight
2026-02-18 17:36 ` Thomas Weißschuh
2026-02-18 22:57 ` David Laight
2026-02-06 19:11 ` [PATCH v2 next 07/11] tools/nolibc/printf: Add support for conversion flags "#- +" and format "%X" david.laight.linux
2026-02-08 15:47 ` Willy Tarreau [this message]
2026-02-08 17:14 ` David Laight
2026-02-08 16:06 ` Willy Tarreau
2026-02-16 19:57 ` Thomas Weißschuh
2026-02-16 22:50 ` David Laight
2026-02-18 17:39 ` Thomas Weißschuh
2026-02-16 20:11 ` Thomas Weißschuh
2026-02-16 22:52 ` David Laight
2026-02-06 19:11 ` [PATCH v2 next 08/11] tools/nolibc/printf: Add support for zero padding and field precision david.laight.linux
2026-02-08 16:16 ` Willy Tarreau
2026-02-08 17:31 ` David Laight
2026-02-06 19:11 ` [PATCH v2 next 09/11] selftests/nolibc: Improve reporting of vfprintf() errors david.laight.linux
2026-02-16 20:05 ` Thomas Weißschuh
2026-02-17 10:48 ` David Laight
2026-02-18 17:48 ` Thomas Weißschuh
2026-02-06 19:11 ` [PATCH v2 next 10/11] selftests/nolibc: Increase coverage of printf format tests david.laight.linux
2026-02-16 20:14 ` Thomas Weißschuh
2026-02-16 20:23 ` Thomas Weißschuh
2026-02-16 22:54 ` David Laight
2026-02-18 17:41 ` Thomas Weißschuh
2026-02-06 19:11 ` [PATCH v2 next 11/11] selftests/nolibc: Use printf("%.*s", n, "") to align output david.laight.linux
2026-02-08 16:20 ` Willy Tarreau
2026-02-16 20:22 ` Thomas Weißschuh
2026-02-06 21:36 ` [PATCH v2 next 00/11] tools/nolibc: Enhance printf() David Laight
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=aYiwC6Fa2oSlmGBp@1wt.eu \
--to=w@1wt.eu \
--cc=david.laight.linux@gmail.com \
--cc=lechain@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@weissschuh.net \
/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