public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bugdal at aerifal dot cx" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug nptl/16630] Use SYSENTER for pthread_cond_broadcast/signal() (i.e. fix "FIXME: Ingo" issue) Date: Tue, 25 Feb 2014 02:04:00 -0000 [thread overview] Message-ID: <bug-16630-131-VysOA8jQHj@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-16630-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=16630 Rich Felker <bugdal at aerifal dot cx> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bugdal at aerifal dot cx --- Comment #1 from Rich Felker <bugdal at aerifal dot cx> --- Ideally this asm will be removed at some point; I think that would resolve this issue automatically. BTW, the idea of letting apps hook __kernel_vsyscall is a very bad one. In order to fix issue #12683, use of __kernel_vsyscall needs to be abandoned for cancellable syscalls. Treating such hooking as a supported usage would preclude fixing a serious open bug. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2014-02-25 2:04 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-02-24 22:41 [Bug nptl/16630] New: " cjones.bugs at gmail dot com 2014-02-25 2:04 ` bugdal at aerifal dot cx [this message] 2014-02-25 4:51 ` [Bug nptl/16630] " cjones.bugs at gmail dot com 2014-02-25 5:47 ` bugdal at aerifal dot cx 2014-02-25 16:11 ` Ondřej Bílka 2014-02-25 7:41 ` cjones.bugs at gmail dot com 2014-02-25 16:12 ` neleai at seznam dot cz 2014-03-01 22:36 ` cjones.bugs at gmail dot com 2014-03-01 23:54 ` bugdal at aerifal dot cx 2014-03-02 0:09 ` cjones.bugs at gmail dot com 2014-03-02 0:13 ` bugdal at aerifal dot cx 2014-06-13 6:48 ` 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-16630-131-VysOA8jQHj@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).