this post was submitted on 26 Sep 2023
15 points (100.0% liked)

Steam Deck

5727 readers
1 users here now

Universal community link
!steamdeck@lemmy.ml

Rules

Order

Models

64GB eMMC LCD
256GB NVMe LCD
512GB NVMe LCD
512GB NVMe OLED
1TB NVMe OLED

Allowed languages

founded 3 years ago
MODERATORS
top 1 comments
sorted by: hot top controversial new old
[–] autotldr@lemmings.world 2 points 11 months ago

This is the best summary I could come up with:


Queued up into the Btrfs file-system driver's "for-next" branch ahead of the Linux 6.7 cycle is the Temp-FSID (Same-FSID) feature that is being pursued for use by Valve's Steam Deck game console.

Such same-fsid mounting is hereby added through the usage of the filesystem feature "temp-fsid" - when such feature is used, btrfs generates a random fsid for the filesystem and leverages the long-term present metadata_uuid infrastructure to enable the usage of this secondary "virtual" fsid, effectively requiring few non-invasive changes to the code and no new potential corner cases.

In order to prevent more code complexity and corner cases, the temp-fsid feature is not allowed when the metadata_uuid flag is present on the fs, or if the device is on fsid-change state.

This functionality has been queued into kdave/linux.git's for-next branch where Btrfs material is staged ahead of the next Linux kernel cycle.

Thus this new Btrfs feature will be found in Linux 6.7 barring any issues from appearing between now and the merge window opening around early November.

This Btrfs feature was also mentioned last week at OSS EU 2023 as part of Valve's upstream contributions to Linux.


The original article contains 462 words, the summary contains 190 words. Saved 59%. I'm a bot and I'm open source!