From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 015763858D28; Sat, 4 Mar 2023 11:33:54 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 015763858D28 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1677929635; bh=hAvexHEZyXcXqyNNAWKBjPVyjSduV0E2l4WzT74IcG4=; h=From:To:Subject:Date:In-Reply-To:References:From; b=b05gtO3T+26dtowo3cmfrPBHsXYaU6a3v0UnBIyK/XWgRPMMlr/69ll9F7C2yurxe ghQyc9O1k2u1N8i6qohd3F3woAyT3zDdR9+ltYgfuvUPZ5hl3ZX6j+/T1lYXHlNXcy LvF61jSP24uGNRIzCFHmsk+/RMwA0M56fcst20z4= From: "stsp at users dot sourceforge.net" To: glibc-bugs@sourceware.org Subject: [Bug dynamic-link/30127] [rfe]: enable ld audit at run-time Date: Sat, 04 Mar 2023 11:33:53 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: dynamic-link X-Bugzilla-Version: 2.38 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: stsp at users dot sourceforge.net 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: 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=3D30127 --- Comment #35 from Stas Sergeev --- (In reply to Jonathon Anderson from comment #33) > So, my group currently assumes la_objopen() happens before the init > constructors of the referenced objects. It turns out to be an important > callback for registering callbacks in runtime libraries before transferri= ng > control back to the application. Is there a way to indicate to the auditor > that it's "missed the boat" so auditors that need this timing can recover > gracefully? So while I added what you asked for, let me wonder why "missed the boat"? It seems gcc allows to specify the constructor priority. So why not to create the "first" constructor for loading audit modules, and actually start trying my patch out in your use-case? :) I think it accumulated everything to aid your scenario. --=20 You are receiving this mail because: You are on the CC list for the bug.=