[Touch-packages] [Bug 2026273] Re: SRU e2fsprogs v1.47.0 for HWE reasons
Ubuntu 23.04 (Lunar Lobster) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: focal (Ubuntu Lunar) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/2026273 Title: SRU e2fsprogs v1.47.0 for HWE reasons Status in e2fsprogs package in Ubuntu: Confirmed Status in focal package in Ubuntu: New Status in e2fsprogs source package in Jammy: Confirmed Status in focal source package in Jammy: New Status in e2fsprogs source package in Kinetic: Won't Fix Status in focal source package in Kinetic: New Status in e2fsprogs source package in Lunar: Won't Fix Status in focal source package in Lunar: Won't Fix Bug description: [ Impact ] * orphan_file ext4 feature is available in Jammy v5.15 GA kernel * It is to be enabled by default in Mantic * fsck utility in jammy doesn't support orphan_file feature * as part of forwards-compatibility support it would be useful for Jammy 22.04 LTS to be able to fsck future releases (i.e. 23.10 / 24.04) * as part of HWE support, users may opt-in and choose to use orphan_file in Jammy today, when they do so they currently loose support to fsck a given filesystem. [ Test Plan ] * Create new ext4 filesystem with GA version of e2fsprogs and with proposed one * Ensure that default feature set enabled is the same (i.e. orphan_file & metadata_csum features are OFF) * Ensure that either fsck can fsck both filesystems * Use tune2fs to enable orphan_file feature * Ensure that new fsck can check such a filesystem, and that GA (v5.15) kernel can mount it * do test rebuilds of reverse-build-depends of e2fsprogs to verify to change of API and ABI, none should FTBFS and none should gain any new dependencies on the 1.47 symbols [ Where problems could occur ] * library api/abi changes: struct ext2_super_block size is unchanged, s_orphan_file_inum consumes one of the s_reserved fields. orphan_file related public APIs are added. * default features: Ensure that config files are unchanged, to ensure that no new features are enabled by default, meaning filesystems created with the upgraded e2fsprogs in a given Ubuntu release will keep the same feature level. [ Other Info ] * Anything else you think is useful to include * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board * and address these questions in advance To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/2026273/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2026273] Re: SRU e2fsprogs v1.47.0 for HWE reasons
Ubuntu 23.04 (Lunar Lobster) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: e2fsprogs (Ubuntu Lunar) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/2026273 Title: SRU e2fsprogs v1.47.0 for HWE reasons Status in e2fsprogs package in Ubuntu: Confirmed Status in focal package in Ubuntu: New Status in e2fsprogs source package in Jammy: Confirmed Status in focal source package in Jammy: New Status in e2fsprogs source package in Kinetic: Won't Fix Status in focal source package in Kinetic: New Status in e2fsprogs source package in Lunar: Won't Fix Status in focal source package in Lunar: Won't Fix Bug description: [ Impact ] * orphan_file ext4 feature is available in Jammy v5.15 GA kernel * It is to be enabled by default in Mantic * fsck utility in jammy doesn't support orphan_file feature * as part of forwards-compatibility support it would be useful for Jammy 22.04 LTS to be able to fsck future releases (i.e. 23.10 / 24.04) * as part of HWE support, users may opt-in and choose to use orphan_file in Jammy today, when they do so they currently loose support to fsck a given filesystem. [ Test Plan ] * Create new ext4 filesystem with GA version of e2fsprogs and with proposed one * Ensure that default feature set enabled is the same (i.e. orphan_file & metadata_csum features are OFF) * Ensure that either fsck can fsck both filesystems * Use tune2fs to enable orphan_file feature * Ensure that new fsck can check such a filesystem, and that GA (v5.15) kernel can mount it * do test rebuilds of reverse-build-depends of e2fsprogs to verify to change of API and ABI, none should FTBFS and none should gain any new dependencies on the 1.47 symbols [ Where problems could occur ] * library api/abi changes: struct ext2_super_block size is unchanged, s_orphan_file_inum consumes one of the s_reserved fields. orphan_file related public APIs are added. * default features: Ensure that config files are unchanged, to ensure that no new features are enabled by default, meaning filesystems created with the upgraded e2fsprogs in a given Ubuntu release will keep the same feature level. [ Other Info ] * Anything else you think is useful to include * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board * and address these questions in advance To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/2026273/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
