public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Shani Leviim <sleviim@redhat.com>
Cc: alx@kernel.org, linux-man@vger.kernel.org,
	automotive-devel@redhat.com,
	"Carlos O'Donell" <carlos@redhat.com>,
	Sergei Gromeniuk <sgromeni@redhat.com>,
	Gobinda Das <godas@redhat.com>
Subject: Re: [patch] strerror.3: Change strerror() reference from MT-Unsafe to MT-Safe
Date: Thu, 13 Jul 2023 10:12:00 +0200	[thread overview]
Message-ID: <878rbk1b8v.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <CAMO6KYomqkRFVnE1gfNa=htbZ5oBrVAm+AsFVqc6+vqZ0YxnAw@mail.gmail.com> (Shani Leviim's message of "Wed, 12 Jul 2023 21:46:37 +0300")

* Shani Leviim:

> @@ -169,6 +172,16 @@ is too small and
>  is unknown).
>  The string always includes a terminating null byte (\(aq\e0\(aq).
>  .\"
> +.PP
> +The automatically generated buffer for
> +.BR strerror ()
> +and
> +.BR strerror_l ()
> +is sufficient to avoid an
> +.B ERANGE
> +error when calling
> +.BR strerror_r ().
> +.PP

I think this gives the wrong impression that the pointer returned by
strerror/strerror_l can be used with strerror_r.  This is not the case
because the application does not own that buffer, or know its length.

Thanks,
Florian


       reply	other threads:[~2023-07-13  8:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAMO6KYomqkRFVnE1gfNa=htbZ5oBrVAm+AsFVqc6+vqZ0YxnAw@mail.gmail.com>
2023-07-13  8:12 ` Florian Weimer [this message]
2023-07-13 11:15   ` [patch] strerror.3: Change strerror() reference from MT-Unsafe to MT-Safe Shani Leviim
2023-07-16 17:28     ` Shani Leviim
2023-07-28 18:55       ` Alejandro Colomar
2023-07-30 13:41         ` Shani Leviim
2023-08-11 22:51           ` Alejandro Colomar
2023-08-13 14:37             ` Shani Leviim
2023-08-13 15:11               ` Alejandro Colomar
2023-08-13 16:58                 ` Shani Leviim
2023-08-13 20:06                   ` Alejandro Colomar
2023-08-13 20:19 ` [PATCH v2] " Alejandro Colomar
2023-08-13 20:21 ` [PATCH v3] " Alejandro Colomar
2023-08-14 10:44   ` 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=878rbk1b8v.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=alx@kernel.org \
    --cc=automotive-devel@redhat.com \
    --cc=carlos@redhat.com \
    --cc=godas@redhat.com \
    --cc=linux-man@vger.kernel.org \
    --cc=sgromeni@redhat.com \
    --cc=sleviim@redhat.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