From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 1BADC385840F; Mon, 14 Nov 2022 16:40:19 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 1BADC385840F DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1668444019; bh=SVytls5DPkkyYAesOtA59X7+riYa1zsO6Z4PwpUOOJI=; h=From:To:Subject:Date:In-Reply-To:References:From; b=drbi0nSaRAi4JeJuHLj5agezzdbzEgOOpaRGcMRQ7NXVGCGZo4T39o5qTKpVNwX2P cXJ0iTzGNODIfqpYzesmsybBWwBtKbT6PvpMMaBDEbLf23E14ZluCbPSugArDWCdrQ /IfqfAWbVLVw+LEosocBXmKAWxAzTzB+d0EK5OG0= From: "mjbaars1977 at gmail dot com" To: glibc-bugs@sourceware.org Subject: [Bug libc/29585] sched_getcpu returns invalid results Date: Mon, 14 Nov 2022 16:40:18 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: libc X-Bugzilla-Version: 2.35 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: mjbaars1977 at gmail dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: INVALID X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: security- X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D29585 --- Comment #25 from Mischa Baars --- If you think that I'm using certain system calls incorrectly, such that undefined behavior from using sched_getcpu() is the result, and pthread_create() does a better job because your code is presumably better than the system calls' code, then why are these SIGCHLD signals missing? For now I see only a threading system that seems to be missing essential bits and pieces. On Mon, 14 Nov 2022, 13:55 fweimer at redhat dot com, < sourceware-bugzilla@sourceware.org> wrote: > https://sourceware.org/bugzilla/show_bug.cgi?id=3D29585 > > --- Comment #23 from Florian Weimer --- > I don't think there is nothing to fix in glibc because you use __clone > incorrectly=E2=80=94and unnecessarily. This issue will not happen with > pthread_create. > > -- > You are receiving this mail because: > You reported the bug. --=20 You are receiving this mail because: You are on the CC list for the bug.=