public inbox for liba2i@lists.linux.dev
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: bug-gnulib@gnu.org
Cc: "Alejandro Colomar" <alx@kernel.org>,
	"Paul Eggert" <eggert@cs.ucla.edu>,
	"Bruno Haible" <bruno@clisp.org>,
	"Đoàn Trần Công Danh" <congdanhqx@gmail.com>,
	"Eli Schwartz" <eschwartz93@gmail.com>,
	"Sam James" <sam@gentoo.org>, "Serge Hallyn" <serge@hallyn.com>,
	"Iker Pedrosa" <ipedrosa@redhat.com>,
	"Michael Vetter" <jubalh@iodoru.org>,
	liba2i@lists.linux.dev
Subject: [PATCH v1 0/2] xstrtol() fixes
Date: Fri, 19 Jul 2024 14:53:26 +0200	[thread overview]
Message-ID: <20240719125312.15885-2-alx@kernel.org> (raw)

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

Hi Paul,

This patch set --hopefully; writing calls to strtol(3) is a PITA-- fixes
the remaining issues I've observed in xstrtol().

Have a lovely day!
Alex

Alejandro Colomar (2):
  xstrtol: Correctly handle an invalid base
  xstrtol: Add defensive check against undocumented errors

 lib/xstrtol.c | 35 +++++++++++++++++++++--------------
 1 file changed, 21 insertions(+), 14 deletions(-)

Range-diff against v0:
-:  ---------- > 1:  9345449d79 xstrtol: Correctly handle an invalid base
-:  ---------- > 2:  d1836c207a xstrtol: Add defensive check against undocumented errors
-- 
2.45.2


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

             reply	other threads:[~2024-07-19 12:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-19 12:53 Alejandro Colomar [this message]
2024-07-19 12:53 ` [PATCH v1 1/2] xstrtol: Correctly handle an invalid base Alejandro Colomar
2024-07-19 13:09   ` Alejandro Colomar
2024-07-19 13:10     ` Alejandro Colomar
2024-07-19 12:53 ` [PATCH v1 2/2] xstrtol: Add defensive check against undocumented errors Alejandro Colomar

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=20240719125312.15885-2-alx@kernel.org \
    --to=alx@kernel.org \
    --cc=bruno@clisp.org \
    --cc=bug-gnulib@gnu.org \
    --cc=congdanhqx@gmail.com \
    --cc=eggert@cs.ucla.edu \
    --cc=eschwartz93@gmail.com \
    --cc=ipedrosa@redhat.com \
    --cc=jubalh@iodoru.org \
    --cc=liba2i@lists.linux.dev \
    --cc=sam@gentoo.org \
    --cc=serge@hallyn.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. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox