Fix crash when PARTNAME is invalid utf-8 #136
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In GPT partitions, the PartitionName field is stored as a utf-16 string. For some reason though, in udev, the value is not converted from utf-16 to utf-8. Instead, the MSB is dropped and the LSB is kept. e.g.,
In the above examples, only the letter A results in a valid UTF-8 character.
When using pyudev, the values are all expected to be decodable using the system's default encoding.
In probert, it can result in a crash when iterating over all the properties of a block device, that are mapped by pyudev.
To work around the issue, we now stop iterating over all the values. We iterate over the keys and only access the value if we need it.
NOTE: pyudev deprecated the use of
Device.__getitem__
,Device.__iter__
and similar constructs to access a pyudev.Device property. Instead, one should useDevice.properties.__getitem__
,Device.properties.__iter__
and so on. In a future version of pyudev, the support for the deprecated constructs will be dropped so we need to start using the recommended alternative.https://bugs.launchpad.net/subiquity/+bug/2017862