From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 23C573846915; Mon, 20 Feb 2023 12:15:47 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 23C573846915 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1676895347; bh=/XOZTh/Ebod6OxrvzwYEaiR7QAa/iSGkV9pYzAaVSh8=; h=From:To:Subject:Date:In-Reply-To:References:From; b=sea7AM6f2x96FEWmgsCESY5FkH9dR98SvJ1fydQDsgW8ckL4F3tpRllqzMTPbz+/c 60BZrwbzpnCttiqLLlqP0uoiwDFZwPiVdwxb6e8bgk2GQbYH0/TwuNJvtSMpgXUAMI BNqdQG3l1WIFQ4cwJkrRQ4tN7Zjx5IuP/mwDJhZA= From: "fweimer at redhat dot com" To: glibc-bugs@sourceware.org Subject: [Bug dynamic-link/30134] DT_AUDIT is ignored for dlopen()ed solib Date: Mon, 20 Feb 2023 12:15:46 +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: 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: 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=3D30134 --- Comment #6 from Florian Weimer --- (In reply to Stas Sergeev from comment #5) > (In reply to Florian Weimer from comment #4) > > We also have hard limits on the number of auditors. The explicit one > > (namespace count) is perhaps somewhat easy to overcome, but there is al= so > > the static TLS space consumption by new auditing namespaces. >=20 > I am yet to understand why every > audit module needs a new NS. Wouldn't > it be possible to use one separate > NS for all audit modules? I don't know. It does seem wasteful. I haven't seen many production example= s of audit modules. Multiple auditors loaded at startup may be rare (even rarer = than auditing itself), so it's possible that we could switch to a single separate namespace without impacting backwards compatibility. If the auditor cannot intercept libc.so.6 calls because it is already loade= d, then it can even use the main libc.so.6, and no fully separate namespace is needed at all. There are many open questions and things to explore in this area. --=20 You are receiving this mail because: You are on the CC list for the bug.=