Package: udisks2
Version: 2.9.2-1
We have some laptops equipped with an eMMC. The eMMC has blocks: /dev/mmcblk0,
/dev/mmcblk0boot0, /dev/mmcblk0boot1, and /dev/mmcblk0rpmb.
We notice udisks_client_get_block_for_drive() always returns the wrong block
/dev/mmcblk0boot1 of eMMC which leads other programs getting wrong behavior.
This bug appears since 2.9.2 including commit ("udev: Propagate mmcblk disk
attributes to mmcblk_boot devices").
This bug is reported to upstream as an issue:
"udisks_client_get_block_for_drive() always returns the wrong block of eMMC" [1]
Thanks to Will Thompson's fix and it has been merged by upstream as the commit
5d0ac7ebefb8 ("udisksclient: Make get_block_for_drive deterministic") [2]
Hope this commit can be included as a patch in the package before the next
upstream release.
[1]: https://github.com/storaged-project/udisks/issues/879
[2]:
https://github.com/storaged-project/udisks/commit/5d0ac7ebefb8b7aad73871936f5011545cc66344
Thanks,
Jian-Hong Pan
