Hi Fabio, On Fri, Sep 12, 2025 at 03:40:28PM +0200, Fabio Valentini wrote: > On Fri, Sep 12, 2025 at 3:36 PM Mark Wielaard <[email protected]> wrote: > > > > As other have pointed out earlier this isn't an accident. This is > > precisely so that when user space observability tools (profilers, > > debuggers, tracers, etc.) are installed they work out of the box. > > But it's also clear that "when user space observability tools are > installed they work out of the box" just isn't true right now, because > the yama_ptrace_scope change is applied on *all* systems, regardless > if those tools were installed or not, since the override file is > pulled in into the *base system* and not just by those tools. (Or, I > guess, it *is* true, by default, since the overrides are *always* in > place, even when those tools *aren't* installed ...)
Yes, technically because libdw (part of elfutils-libs) provides interprocess inspection any package depending on that library pulls in default-yama-scope whether or not they use that functionality. Given abrt and systemd-coredump use libdw to produce backtraces it pretty much means that is already true. Ideally the default-yama-scope would only be pulled in by leaf packages. But since with the current setup most things just work by default it seems that was good enough. Cheers, Mark -- _______________________________________________ devel mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected] Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
