Add: Qualcomm User Data Encryption test script & Document

[xbharani]

• Checks for fscryptctl binary presence
• Creates a random sw encryption key
• Applies and verifies encryption policy
• Confirms functionality with a test file

[github-actions]

This pull request has been marked as stale due to 30 days of inactivity. To prevent automatic closure in 7 days, remove the stale label or add a comment. You can reopen a closed pull request at any time.

[smuppand]

@xbharani Any update on the requested changes?

[github-actions]

This pull request has been marked as stale due to 30 days of inactivity. To prevent automatic closure in 7 days, remove the stale label or add a comment. You can reopen a closed pull request at any time.

[smuppand]

the script is close, but a few things will bite in CI / reliability, plus a couple of correctness/safety issues.

[smuppand]

A few additional minor changes are required. Other than that, everything appears to be fine.

[smuppand]

Few nice to have changes

[smuppand]

Still few must fix items.

[smuppand]

if there's any chance of a busybox/ non-GNU environment, just be aware --output=target may not exist. Given the meta-qcom target, it's probably fine. If we want to be ultra-portable in future, this part might be abstracted into hlper, but for now it's acceptable.

Still it is not addressed. This is ok most of the time. But it can include leading spaces depending on the df output formatting.

safer
FS_PATH="$(df --output=target "$MOUNT_DIR" 2>/dev/null | awk 'NR==2{print $1}')"

[smuppand]

Minor NIT changes.

[smuppand]

@xbharani please respond to the comments where you have addressed. Otherwise it is hard to find what has been addressed.

[smuppand]

LGTM