** Description changed: [ Impact ] - * An explanation of the effects of the bug on users and justification - for backporting the fix to the stable release. + In order to help developers with profiling, Ubuntu enabled frame- + pointers for packages in the main archive. - * In addition, it is helpful, but not required, to include an - explanation of how the upload fixes this bug. + https://ubuntu.com/blog/ubuntu-performance-engineering-with-frame- + pointers-by-default + + The `Affects` packages were missed due to the packaging issues. These + have been fixed on Oracular and can now be ported to Noble. + [ Test Plan ] - * detailed instructions how to reproduce the bug + Look at the DW_AT_producer in the associated debug ELF file for flags. + -fno-omit-frame-pointer should be present after the fix. - * these should allow someone who is not familiar with the affected - package to reproduce the bug and verify that the updated package - fixes the problem. - - * if other testing is appropriate to perform before landing this - update, this should also be described here. + The following scripts can be used as reference + https://gist.github.com/julian-klode/85e55553f85c410a1b856a93dce77208 + https://gist.github.com/julian-klode/95818246eaef0ac6a54588f7f368e25c [ Where problems could occur ] - * Think about what the upload changes in the software. Imagine the - change is wrong or breaks something else: how would this show up? - - * It is assumed that any SRU candidate patch is well-tested before - upload and has a low overall risk of regression, but it's important - to make the effort to think about what ''could'' happen in the event - of a regression. - - * This must never be "None" or "Low", or entirely an argument as to why - your upload is low risk. - - * This both shows the SRU team that the risks have been considered, - and provides guidance to testers in regression-testing the SRU. + No source changes are made. The packaging fixes have enabled other + security hardening flags. This could have unintended effects. [ Other Info ] - * Anything else you think is useful to include + changes in dpkg have been made to make sure frame-pointers are not + enabled on s390x and ppc64el. - * Anticipate questions from users, SRU, +1 maintenance, security teams - and the Technical Board and address these questions in advance + Bug reference with similar SRU - + https://bugs.launchpad.net/ubuntu/+source/ipvsadm/+bug/2071949
** Description changed: [ Impact ] In order to help developers with profiling, Ubuntu enabled frame- pointers for packages in the main archive. https://ubuntu.com/blog/ubuntu-performance-engineering-with-frame- pointers-by-default The `Affects` packages were missed due to the packaging issues. These have been fixed on Oracular and can now be ported to Noble. - [ Test Plan ] Look at the DW_AT_producer in the associated debug ELF file for flags. -fno-omit-frame-pointer should be present after the fix. The following scripts can be used as reference https://gist.github.com/julian-klode/85e55553f85c410a1b856a93dce77208 https://gist.github.com/julian-klode/95818246eaef0ac6a54588f7f368e25c + + <package specific test plan goes here> [ Where problems could occur ] No source changes are made. The packaging fixes have enabled other security hardening flags. This could have unintended effects. [ Other Info ] changes in dpkg have been made to make sure frame-pointers are not enabled on s390x and ppc64el. Bug reference with similar SRU - https://bugs.launchpad.net/ubuntu/+source/ipvsadm/+bug/2071949 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081707 Title: [SRU] Please enable frame-pointer on Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/authbind/+bug/2081707/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
