| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| udisksclient-Make-get_block_for_drive-deterministic.patch | udisksclient: Make get_block_for_drive deterministic While any given Block object has at most one corresponding Drive, many Block objects may share the same Drive. One example is eMMC devices which provide a block device for the main data area (e.g. /dev/mmcblk0) as well as additional logical block devices for device partitions (e.g. /dev/mmcblk0boot0 and /dev/mmcblk0boot1). This behaviour was introduced in #834 to resolve issue #619 that these device partitions caused a phantom additional Drive object to be exposed. On that issue, I wrote: > I believe that Block.Drive on the boot partitions should point to the > same data area as the main data area (and its logical partitions); > udisks_client_get_block_for_drive() on the drive should return > /org/freedesktop/UDisks2/block_devices/mmcblk0. The first part is now true, but as described on #879 the second part is not true. It is now non-deterministic which Block will be returned, based only on the order of objects returned by g_dbus_object_manager_get_objects(). Make the return value of udisks_client_get_block_for_drive() deterministic by sorting the list of candidate Block objects by their device path in lexicographic order. Since (e.g.) /dev/mmcblk0 sorts before /dev/mmcblk0boot0, this has the desirable side-effect that calling udisks_client_get_block_for_drive() on an eMMC Drive returns the 'real' Block for the main data area. Fixes #879. (cherry picked from commit 5d0ac7ebefb8b7aad73871936f5011545cc66344) |
Will Thompson <wjt@endlessos.org> | no | 2021-04-21 | ||
| Use-the-mkfs-command-to-format-exfat-partitions.patch | Use the mkfs command to format exfat partitions The currently used mkexfatfs is only available in exfat-utils and not in the new exfatprogs. https://github.com/storaged-project/udisks/issues/882 (cherry picked from commit 1c13dc64213554f979b24788b40398fee7a5039f) |
Sebastien Bacher <seb128@ubuntu.com> | no | 2021-04-21 | ||
| mount-options-Always-use-errors-remount-ro-for-ext-filesy.patch | mount options: Always use errors=remount-ro for ext filesystems Default mount options are focused primarily on data safety, mounting damaged ext2/3/4 filesystem as readonly would indicate something's wrong. (cherry picked from commit 2d5d2b7570b0f44c14b34b5dc831f174205c10f2) (cherry picked from commit 38d90a433bda0fc0f2a409f6baa12c3958893571) |
Tomas Bzatek <tbzatek@redhat.com> | no | 2021-09-15 |