public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sstewartgallus00 at mylangara dot bc.ca" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug nptl/12683] Race conditions in pthread cancellation Date: Sun, 20 Jul 2014 18:15:00 -0000 [thread overview] Message-ID: <bug-12683-131-o7sPqxRoct@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-12683-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=12683 --- Comment #21 from Steven Stewart-Gallus <sstewartgallus00 at mylangara dot bc.ca> --- Okay Rich Felker, I was confused because the implementation in Musl seems to look it'd would make syscall users that block cancellation points. So, if GLibc does something similar to your solution they would have to explicitly block cancels in the syscall function to preserve compatibility (and in the future GLibc might possibly consider moving over to making syscall automatically cancellable for blocking system calls but that'd be a separate issue)? -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2014-07-20 18:15 UTC|newest] Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-04-18 22:28 [Bug nptl/12683] New: " bugdal at aerifal dot cx 2011-04-18 22:35 ` [Bug nptl/12683] " bugdal at aerifal dot cx 2011-09-21 18:30 ` bugdal at aerifal dot cx 2012-04-29 2:56 ` bugdal at aerifal dot cx 2012-04-29 2:57 ` bugdal at aerifal dot cx 2012-09-22 23:13 ` bugdal at aerifal dot cx 2013-08-16 15:32 ` carlos at redhat dot com 2013-08-16 15:34 ` carlos at redhat dot com 2013-08-16 15:34 ` carlos at redhat dot com 2013-08-16 16:22 ` bugdal at aerifal dot cx 2013-08-16 16:59 ` carlos at redhat dot com 2013-08-16 17:14 ` bugdal at aerifal dot cx 2013-08-16 18:09 ` carlos at redhat dot com 2014-01-10 20:25 ` carlos at redhat dot com 2014-01-10 21:31 ` carlos at redhat dot com 2014-01-10 22:37 ` bugdal at aerifal dot cx 2014-01-12 18:31 ` carlos at redhat dot com 2014-01-12 23:55 ` bugdal at aerifal dot cx 2014-01-13 1:52 ` carlos at redhat dot com 2014-01-13 4:37 ` bugdal at aerifal dot cx 2014-01-14 14:51 ` carlos at redhat dot com 2014-02-16 19:42 ` jackie.rosen at hushmail dot com 2014-05-28 19:47 ` schwab at sourceware dot org 2014-05-28 19:47 ` schwab at sourceware dot org 2014-06-27 13:35 ` fweimer at redhat dot com 2014-07-19 18:44 ` sstewartgallus00 at mylangara dot bc.ca 2014-07-19 18:54 ` bugdal at aerifal dot cx 2014-07-20 18:15 ` sstewartgallus00 at mylangara dot bc.ca [this message] 2014-07-20 18:41 ` bugdal at aerifal dot cx 2014-08-19 14:08 ` azanella at linux dot vnet.ibm.com 2014-08-28 15:02 ` carlos at redhat dot com 2015-01-15 13:20 ` dan at censornet dot com 2015-01-15 13:31 ` bugdal at aerifal dot cx 2015-01-15 14:01 ` dan at censornet dot com 2020-06-08 14:04 ` fweimer at redhat dot com
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-12683-131-o7sPqxRoct@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: linkBe 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).