public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "schwab@linux-m68k.org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/29585] sched_getcpu returns invalid results Date: Wed, 28 Sep 2022 10:09:11 +0000 [thread overview] Message-ID: <bug-29585-131-HgV5raICbA@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-29585-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=29585 --- Comment #12 from Andreas Schwab <schwab@linux-m68k.org> --- clone without CLONE_VM is the same as fork (but without running the fork handlers you still get undefined behaviour). -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2022-09-28 10:09 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-19 8:22 [Bug libc/29585] New: " mjbaars1977 at gmail dot com 2022-09-19 14:21 ` [Bug libc/29585] " fweimer at redhat dot com 2022-09-21 8:00 ` mjbaars1977 at gmail dot com 2022-09-22 8:30 ` mjbaars1977 at gmail dot com 2022-09-22 12:59 ` mjbaars1977 at gmail dot com 2022-09-22 13:00 ` mjbaars1977 at gmail dot com 2022-09-26 8:04 ` mjbaars1977 at gmail dot com 2022-09-26 9:18 ` fweimer at redhat dot com 2022-09-26 11:14 ` mjbaars1977 at gmail dot com 2022-09-26 11:21 ` fweimer at redhat dot com 2022-09-26 12:15 ` mjbaars1977 at gmail dot com 2022-09-28 9:59 ` mjbaars1977 at gmail dot com 2022-09-28 10:09 ` schwab@linux-m68k.org [this message] 2022-09-28 14:03 ` mjbaars1977 at gmail dot com 2022-10-10 9:18 ` fweimer at redhat dot com 2022-10-10 15:14 ` mjbaars1977 at gmail dot com 2022-10-10 16:20 ` mjbaars1977 at gmail dot com 2022-10-10 16:31 ` fweimer at redhat dot com 2022-10-10 16:41 ` mjbaars1977 at gmail dot com 2022-10-10 17:05 ` mjbaars1977 at gmail dot com 2022-10-10 17:09 ` schwab@linux-m68k.org 2022-10-10 17:10 ` mjbaars1977 at gmail dot com 2022-11-14 9:58 ` mjbaars1977 at gmail dot com 2022-11-14 12:55 ` fweimer at redhat dot com 2022-11-14 16:15 ` mjbaars1977 at gmail dot com 2022-11-14 16:40 ` mjbaars1977 at gmail 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-29585-131-HgV5raICbA@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).