disable shiftfs
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Triaged
|
Medium
|
Unassigned | ||
Mantic |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
[Impact]
Now that all the filesystems that we officially support have the idmapped mounts capability we can get rid of shiftfs.
The benefit of this change is that we don't have to maintain an out-of-tree filesystem anymore and we can completely rely on upstream features.
[Test case]
lxd was the main user of shiftfs to compensate the lack of idmapped mounts capability of certain filesystems, such as zfs / ceph, but now in mantic also these two filesystem received the support for idmapped mounts (support for zfs was introduced in 2.2.0~rc3 and for ceph see LP: #2032959).
The lxd team provided a positive feedback, testing the latest 6.5 Mantic kernel across all the supported filesystems with shiftfs disabled.
[Fix]
Disable shiftfs in the kernel config and enable unsafe idmapped mounts by default (default=on).
[Regression potential]
The support for idmapped mounts for the ceph filesystem is not applied upstream yet, so we may experience regressions in systems that are using this filesystem. Moreover disabling shiftfs may trigger failures in our testing (testing shiftfs capabilities will obviously fail) or break any other user-space application that is relying on shiftfs (however to our knowledge lxd was the only "official" user or shiftfs; for this reason we may also see potential regressions in lxd).
Changed in linux (Ubuntu Mantic): | |
status: | Incomplete → Triaged |
Changed in linux (Ubuntu Mantic): | |
importance: | Undecided → Medium |
Changed in linux (Ubuntu Mantic): | |
status: | Triaged → Fix Committed |
tags: |
added: verification-done-mantic removed: verification-needed-mantic-linux |
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
apport-collect 2038522
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.