* Jeff Law: > If I'm understanding things correctly, the original proposal is trying > to make a very special case of profiling work better -- a case that > 99.9% of Fedora users do not need or care about. That seems like a > particularly bad cost/benefit for this proposal. It became clear during yesterday's meeting that the actual goal is to enable userspace backtraces that can be analyzed by BPF (in the kernel), so it's not really about profiling. Instead it's about enhancing the capabilities of BPF. Nobody mentioned this explicitly, but I expect one could enhance osquery with this and push out BPF-based behavioral analysis using osquery. There is already some BPF support in osquery: Process and socket auditing with osquery <https://osquery.readthedocs.io/en/latest/deployment/process-auditing/> There really should be a way to reach that goal in a more direction, without having to rebuild the entire distribution with different compiler flags. The core issue here is that kernel people boycott both x86 hardware shadow stacks *and* DWARF, which means that the most obvious approaches are not available to us. Thanks, Florian _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx 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/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
