[PATCH] manual: Mark setlogmask as AS-unsafe and AC-unsafe.

[Frederic Berat]

On Thu, Feb 20, 2025 at 4:44 PM Carlos O'Donell <carlos@redhat.com> wrote:

> This fixes the check-safety.sh failure with commit
> ad9c4c536115ba38be3e63592a632709ec8209b4, and correctly marks
> the function AS-unsafe and AC-unsafe due to the use of the
> non-recursive lock.
>

Agreed. Fix for bug 26100 introduced a new lock that wasn't there before,
making the routine AC-unsafe.

LGTM.
Reviewed-by: Frédéric Bérat <fberat@redhat.com>


>
> Tested on x86_64 without regressions.
> ---
>  manual/syslog.texi | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/manual/syslog.texi b/manual/syslog.texi
> index 90a6487c02..9875793b49 100644
> --- a/manual/syslog.texi
> +++ b/manual/syslog.texi
> @@ -498,7 +498,7 @@ The symbols referred to in this section are declared
> in the file
>
>  @deftypefun int setlogmask (int @var{mask})
>  @standards{BSD, syslog.h}
> -@safety{@prelim{}@mtsafe{}@asunsafe{}@acsafe{}}
> +@safety{@prelim{}@mtsafe{}@asunsafe{@asulock{}}@acunsafe{@aculock{}}}
>
>  @code{setlogmask} sets a mask (the ``logmask'') that determines which
>  future @code{syslog} calls shall be ignored.  If a program has not
> --
> 2.48.1
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://sourceware.org/pipermail/libc-alpha/attachments/20250220/4668f284/attachment-0001.htm>