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/17214] New: Expose a function to reset the PID cache Date: Tue, 29 Jul 2014 21:23:00 -0000 [thread overview] Message-ID: <bug-17214-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=17214 Bug ID: 17214 Summary: Expose a function to reset the PID cache Product: glibc Version: unspecified Status: NEW Severity: normal Priority: P2 Component: nptl Assignee: unassigned at sourceware dot org Reporter: sstewartgallus00 at mylangara dot bc.ca CC: drepper.fsp at gmail dot com GLibc caches PIDs. Much has been said about this. Regardless, some people have to use the low level clone system call which does not update the PID cache (for making new processes only, trying to make one's own threads that interact with NPTL would be a mess). I would like a way to reset the PID cache so that the low level clone system call is usable. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2014-07-29 21:23 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-07-29 21:23 sstewartgallus00 at mylangara dot bc.ca [this message] 2014-07-30 4:07 ` [Bug nptl/17214] " carlos at redhat dot com 2014-07-30 17:39 ` sstewartgallus00 at mylangara dot bc.ca 2014-07-30 17:41 ` sstewartgallus00 at mylangara dot bc.ca 2014-07-31 23:25 ` carlos at redhat dot com 2014-08-01 21:59 ` sstewartgallus00 at mylangara dot bc.ca 2014-08-26 4:38 ` bugdal at aerifal dot cx 2014-08-26 18:11 ` sstewartgallus00 at mylangara dot bc.ca 2014-08-26 18:31 ` sstewartgallus00 at mylangara dot bc.ca 2014-10-30 22:01 ` rickyz at chromium dot org 2014-12-18 0:15 ` jld at mozilla dot com 2014-12-18 23:58 ` [Bug nptl/17214] Expose a clone variant that shares stacks instead of jumping to a new one sstewartgallus00 at mylangara dot bc.ca 2014-12-19 0:13 ` sstewartgallus00 at mylangara dot bc.ca 2014-12-19 1:17 ` bugdal at aerifal dot cx 2014-12-19 20:29 ` sstewartgallus00 at mylangara dot bc.ca 2014-12-19 21:01 ` bugdal at aerifal dot cx 2015-01-26 22:33 ` sstewartgallus00 at mylangara dot bc.ca
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-17214-131@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).