public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "carlos at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug nptl/14744] kill -32 $pid or kill -33 $pid on a process cancels a random thread
Date: Sun, 12 Jan 2014 18:34:00 -0000	[thread overview]
Message-ID: <bug-14744-131-2nMQJ1ivz2@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-14744-131@http.sourceware.org/bugzilla/>

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

--- Comment #4 from Carlos O'Donell <carlos at redhat dot com> ---
(In reply to Carlos O'Donell from comment #3)
> However the implementation comment seems to indicate desiring support for
> cancellation from another process?
> 
>       /* We are canceled now.  When canceled by another thread this flag
>          is already set but if the signal is directly send (internally or
>          from another process) is has to be done here.  */
>       int newval = oldval | CANCELING_BITMASK | CANCELED_BITMASK;
> 
> I can't imagine under what use case you would support cancelling a thread in
> a process from another process?

The worrisome bit is the "internally" part which seems to indicate there is
some path inside glibc which can't set the target thread's cancellation status
to "cancelling" which would make it impossible to determine if you should or
should not act on the SIGCANCEL signal (assuming AC-enabled).

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


  parent reply	other threads:[~2014-01-12 18:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-20  1:36 [Bug nptl/14744] New: " bugdal at aerifal dot cx
2014-01-10 20:29 ` [Bug nptl/14744] " carlos at redhat dot com
2014-01-10 22:07 ` neleai at seznam dot cz
2014-01-10 22:43 ` bugdal at aerifal dot cx
2014-01-12 18:32 ` carlos at redhat dot com
2014-01-12 18:34 ` carlos at redhat dot com [this message]
2014-01-12 23:25 ` bugdal at aerifal dot cx
2014-01-16 16:47 ` carlos at redhat dot com
2014-06-14 12:50 ` fweimer at redhat dot com
2021-06-10  1:44 ` 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-14744-131-2nMQJ1ivz2@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).