From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 3E2B33858C1F; Mon, 14 Nov 2022 16:15:13 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 3E2B33858C1F DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1668442513; bh=oPiRkOgKBM9JB8z+DvCwCepOtCAw1Gi7CPeiBbfGiMo=; h=From:To:Subject:Date:In-Reply-To:References:From; b=nthB4Fqe2H2vXKMNAVUM7Yi4NTKp7xw8eij/LeRuYnXPJpUJWct+0UyGmSo3PkJpq Mh8j3OJiuwM9arLbBN8sklUZcREQ2blXAObkUCAxjqdICWKrPACSa74h7zD0hyK9mS SMiEzww1BI8QjLxcAAfDwlW6HUCIVkmvBwRycxaQ= 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:15:11 +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 #24 from Mischa Baars --- Ok, I see. I can try pthread_create, but that doesn't fix the phenomenon. Neither does it fix missing SIGCHLD signals on fork()/clone() termination. However unimportant that seems to you now, there are other (SIGPOLL) signals missing as well, that are from my point of view, essential when trying to distribute tasks across the network. In trying so, I was only able to come up with a client (connected to four servers) take consumes 84% processor time in it's main loop, because waiting for SIGPOLL fails each time and again. 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.=