On 3/17/25 4:01 AM, ZhangHui wrote:
On Android devices, we found that there is a probability that the ufs has been shut down but the thread is still deleting the key, which will cause the bus error.
How does this patch guarantee that crypto keys are evicted before the UFS driver has been shut down? This should be explained in detail in the patch description.
Let's fixed this issue by adding a lock in program_key flow.
There are multiple synchronization objects owned by the UFS driver. Why 'host_sem' and not any other synchronization object? Thanks, Bart.
