diff options
| author | Lee Chee Yang <chee.yang.lee@intel.com> | 2021-01-01 14:18:28 +0800 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2021-01-09 09:17:17 +0000 |
| commit | f00be81c5b85900745a3bd67ad2e212e24613aff (patch) | |
| tree | 92455737a1e8296221bfbdbf5771cf477d569a7c /bitbake/lib/progressbar/compat.py | |
| parent | b1007a891f0457d6c9917efabf1c62afec93c23f (diff) | |
| download | poky-f00be81c5b85900745a3bd67ad2e212e24613aff.tar.gz | |
wic/direct/kparser: ensure fsuuid for vfat and msdos align with format
vfat/msdos filesystem should have fsuuid in format 0xYYYYYYYY where "0x"
in front follow with 8 hexadecimal number in uppercase. In wic, when using
custom fsuuid for vfat/msdos partition in wks, it is able to set the value
in any length, with or without leading "0x". This can cause fsuuid
missaligned when fstab updates, fstab expect exactly 10 character
fsuuid for vfat/msdos partition and all in uppercase.
if custom fsuuid for vfat/msdos is set, check the length and format,
error if it exceed the format size. Amend it so it is align with format
0xYYYYYYYY. This is done before image create and fstab update to ensure the
fsuuid are same in all followup process. if custom fsuuid length less than
expected, fill in "0".
[YOCTO #14161]
(From OE-Core rev: 974e09f3460a27c85a599d8269e3dea66df5ddd2)
Signed-off-by: Lee Chee Yang <chee.yang.lee@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
(cherry picked from commit d9686ae511ef10a504becfd81bfe296b788e1456)
Signed-off-by: Steve Sakoman <steve@sakoman.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'bitbake/lib/progressbar/compat.py')
0 files changed, 0 insertions, 0 deletions