SRU e2fsprogs v1.47.0 for HWE reasons
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
e2fsprogs (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
Jammy |
Confirmed
|
Undecided
|
Unassigned | ||
Kinetic |
Won't Fix
|
Undecided
|
Unassigned | ||
Lunar |
Won't Fix
|
Undecided
|
Unassigned | ||
focal (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Jammy |
New
|
Undecided
|
Unassigned | ||
Kinetic |
Won't Fix
|
Undecided
|
Unassigned | ||
Lunar |
Won't Fix
|
Undecided
|
Unassigned |
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-
* 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-
[ 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
summary: |
- SRU e2fsprogs for HWE reasons + SRU e2fsprogs v1.47.0 for HWE reasons |
Ubuntu 22.10 (Kinetic Kudu) has reached end of life, so this bug will not be fixed for that specific release.