public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug malloc/29624] errno is not cleared when entering main
Date: Fri, 12 Jan 2024 13:24:36 +0000	[thread overview]
Message-ID: <bug-29624-131-8jIWPzQV10@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29624-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=29624

--- Comment #2 from Sourceware Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Andreas K. Huttel
<dilfridge@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=5a85786a9005722be7cb9e70f8874a5f1130daea

commit 5a85786a9005722be7cb9e70f8874a5f1130daea
Author: Xi Ruoyao <xry111@xry111.site>
Date:   Thu Jan 4 21:41:20 2024 +0800

    Make __getrandom_nocancel set errno and add a _nostatus version

    The __getrandom_nocancel function returns errors as negative values
    instead of errno.  This is inconsistent with other _nocancel functions
    and it breaks "TEMP_FAILURE_RETRY (__getrandom_nocancel (p, n, 0))" in
    __arc4random_buf.  Use INLINE_SYSCALL_CALL instead of
    INTERNAL_SYSCALL_CALL to fix this issue.

    But __getrandom_nocancel has been avoiding from touching errno for a
    reason, see BZ 29624.  So add a __getrandom_nocancel_nostatus function
    and use it in tcache_key_initialize.

    Signed-off-by: Xi Ruoyao <xry111@xry111.site>
    Reviewed-by: Adhemerval Zanella  <adhemerval.zanella@linaro.org>
    Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org>

-- 
You are receiving this mail because:
You are on the CC list for the bug.

      parent reply	other threads:[~2024-01-12 13:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-28 10:31 [Bug malloc/29624] New: " ycliang at andestech dot com
2022-09-30 18:27 ` [Bug malloc/29624] " adhemerval.zanella at linaro dot org
2024-01-12 13:24 ` cvs-commit at gcc dot gnu.org [this message]

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=bug-29624-131-8jIWPzQV10@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).