From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 071643858C54; Mon, 14 Nov 2022 09:58:48 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 071643858C54 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1668419929; bh=zNz3yVXpu19CG9WvB6yXYbQeM1ss9HSxUftwJU50D/4=; h=From:To:Subject:Date:In-Reply-To:References:From; b=d5HrG6IyhtZU7JZhaScWqQnaN+1fXxwbpFn6I7lelyhDce1e1/cdLaJa8gS2y6ERA ZB761MBSrIfiz1Zhl5UqeTdd+ZbNUEOZE8y46wY8tsYUS2lXxpbuHF3vbmXS46WwvD v3k0vP5ulbbyovUm5NjWHAxMUCa7x2hI2ILKlSUQ= 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 09:58:48 +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 #22 from Mischa Baars --- (In reply to Florian Weimer from comment #14) > I wonder if we are approaching this from the wrong angle. >=20 > What would we have to change so that you can use pthread_create for your = use > case? Then these issues with glibc interoperability would go away. Hi Florian, I've just checked out the master branch, and if I'm correct nothing has cha= nged in sched_getcpu() since our last correspondence, or actually nothing has changed since version 2.35. Were you or anyone else responsible for the maintenance of glibc planning to fix the issue described in this thread or was that not even part of the pla= n? Best regards, Mischa Baars. --=20 You are receiving this mail because: You are on the CC list for the bug.=