From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 56F5C385140B; Fri, 21 Oct 2022 08:54:26 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 56F5C385140B DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1666342466; bh=tRrrFg+bH+nWzMsFDQLu5PwMyBYYyr8Zos4GLRv3fQk=; h=From:To:Subject:Date:In-Reply-To:References:From; b=AFl8UhUUTp2sREZhosWIz7XDrSlzdgvMo5a+w0Cqp6R+6dVxAifZPBsxaDZYj0H2t PUjAVuU5s4QtA2oTDUkSsNJj2WupTpwIgyjuFa6TNYpRz7PhyPFG+UbmqdbZPE/csB eybT2JTfcNWjZvLMmPEsZi8j3B94kWABDOHKWDOE= From: "fweimer at redhat dot com" To: glibc-bugs@sourceware.org Subject: [Bug time/29705] libc timer_create with option SIGEV_THREAD system call having memory leaks after timer_delete system call Date: Fri, 21 Oct 2022 08:54:25 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: time X-Bugzilla-Version: 2.31 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: fweimer at redhat dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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=3D29705 Florian Weimer changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fweimer at redhat dot com --- Comment #3 from Florian Weimer --- We don't really know if all but one thread have been stopped when __libc_freeres is called by the leak detector. valgrind does this, but other callers might not or might not have the capability to do that because Linux does not provide it. If those threads are still running, bad things will happen if we free the D= TV and other per-thread data. The best thing we can probably do here is not to use malloc to allocate DTVs and other low-level per-thread data structures, effectively hiding these allocations from the leak detector. --=20 You are receiving this mail because: You are on the CC list for the bug.=