Why does the FCS‑client abort during provision‑data retrieval when the number of owner‑root‑hash slots is changed to 5?

Description

After provisioning 5 owner root hash, FCS client aborts during get provision data command

command for fcs-client on get provision data (read efuse) :

./fcs_client –G <name>.bin -p --loglevel=4

Error message displayed when perform command fcs-client on get provision data on 5 owner root hash:

root@agilex:~# fcs_client -G a.bin -p --loglevel=4

        [dbg:]Retrieving provision data
        [dbg:]sysfs attribute /sys/kernel/fcs_sysfs/prov_data
        munmap_chunk(): invalid pointer
        Aborted

perform owner root hash cancellation for root2,root3, and root4, get provision data command from FCS-client still remain “0”.

command for fcs-client cancel owner root :

./fcs_client –c <name>.ccert –c <volatile = 1 / non-volatile =0> 

Error message displayed when perform command fcs-client on get provision data on 5 owner root after perform owner root hash cancellation for root2,root3 and root4:

root@agilex :~# fcs_client -C signed_root4_cancel.ccert -c 1
root@agilex :~# fcs_client -C signed_root3_cancel.ccert -c 1
root@agilex :~# fcs_client -C signed_root2_cancel.ccert -c 1
root@agilex :~# fcs_client -G a.bin -p

W0:Provision Status Code: 0x0
W1:Key Cancellation Status: 0x7F
W2:Co-Sign Status:          0
W2:RootHash0 Cancel Status: 0
W2:RootHash1 Cancel Status: 0
W2:RootHash2 Cancel Status: 4
W2:RootHash3 Cancel Status: 0
W2:RootHash4 Cancel Status: 0
W2:Number of Hashes:        5
W2:Type of Hash:            secp384r1

Resolution

To avoid this problem, upgrade the libfcs with install the following patch:

• fix_read_provision_5_root_hash_v2.patch

This problem is scheduled to be resolved in a future release of the libfcs.