public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "adhemerval.zanella at linaro dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug nptl/25765] Incorrect futex syscall in __pthread_disable_asynccancel for linux x86_64 leads to livelock
Date: Thu, 02 Apr 2020 12:22:50 +0000	[thread overview]
Message-ID: <bug-25765-131-fuM7I8ljgU@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-25765-131@http.sourceware.org/bugzilla/>

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

Adhemerval Zanella <adhemerval.zanella at linaro dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |adhemerval.zanella at linaro dot o
                   |                            |rg

--- Comment #1 from Adhemerval Zanella <adhemerval.zanella at linaro dot org> ---
Thanks for the report, recently I submitted a patch to just remove all the
x86_64 assembly (the cancellation syscalls are now only done by C
implementation, so there is no need to use specialized assembly routines).

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

  reply	other threads:[~2020-04-02 12:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-02 12:08 [Bug nptl/25765] New: " martin.lubich at gmx dot at
2020-04-02 12:22 ` adhemerval.zanella at linaro dot org [this message]
2020-04-02 12:25 ` [Bug nptl/25765] " martin.lubich at gmx dot at
2020-04-02 12:27 ` adhemerval.zanella at linaro dot org
2020-04-03 14:17 ` cvs-commit at gcc dot gnu.org
2020-04-03 14:36 ` adhemerval.zanella at linaro dot org

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-25765-131-fuM7I8ljgU@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).